Communication device, system, and method for active control of external vehicle components

ABSTRACT

The present disclosure includes a system, method, and device related to data collection and communication related to after-market and external vehicle systems, such as towing systems, cargo carrying systems, trailer breakaway systems, brake systems, braking control systems, and the like. Data is sensed, processed, shared, and further leveraged throughout the discrete components of the system, and possibly via internet and other communications&#39; links, to effect various beneficial actions with minimal driver/user interaction or intervention. In the same manner, data from the system may be used for diagnostic reasons, safety controls, and other purposes.

CROSS-REFERENCE TO RELATED APPLICATION

This application is a continuation of U.S. patent application Ser. No.16/534,264, filed on Aug. 7, 2019, titled “COMMUNICATION DEVICE, SYSTEM,AND METHOD FOR ACTIVE CONTROL OF EXTERNAL VEHICLE COMPONENTS, which is acontinuation of U.S. patent application Ser. No. 15/681,729, filed onAug. 21, 2017, titled “COMMUNICATION DEVICE, SYSTEM, AND METHOD FORACTIVE CONTROL OF EXTERNAL VEHICLE COMPONENTS”, which is a continuationof U.S. patent application Ser. No. 15/261,312, filed on Sep. 9, 2016,titled “Communication Device, System and Method for Active Control ofExternal Vehicle Components,” now U.S. Pat. No. 9,738,125, which claimsthe benefit of U.S. Patent Application No. 62/337,692, filed on May 17,2016, titled “Towing Data Collection and Communication Device, Systemand Method,” which are all hereby incorporated by reference in theirentirety.

TECHNICAL FIELD

The present invention relates to a device, system and method forcontrolling external vehicle components. More specifically, an activesystem for sensing and responding to data collected by any number ofdevices associated with a vehicle, for purposes such as towing, brakecontrol, additional cargo carrying, safety systems, and the like, iscontemplated.

BACKGROUND

Integrated (i.e., included or provided as part of the originalmanufacture) diagnostics systems for vehicles, such as cars and trucks,may be used to generate on-board diagnostic or “telematics” informationdescribing the vehicle's location and diagnostic conditions. Thesediagnostic systems typically operate on a communication protocol thatcollects diagnostic information from sensors built into the vehicleitself and then processes the information via an on-board computer, andthen make it available through a 6- or 9-pin connector or other on boarddiagnostic (OBD) connector, which is usually located in the vehicle'sinterior. This information generally relates only to the vehicle itself.

These integrated systems present several limitations. First, except forunique intra-vehicle control functions like antilock brakes andself-parking, they are largely passive in that the information generallyrelates only to the status of operation of the vehicle itself. Secondly,these integrated systems usually add considerable cost. Third, thesystems are deliberately engineered to prevent quick alterations orupdates by the end user or unauthorized parties, thereby making thesystems difficult to improve or change. As such, these systemseffectively operate in a “closed” environment by preventing the end userfrom accessing or using the data generated for other purposes (such astowing systems and other products described below).

Further, it must be noted that specialized vehicles (i.e., vehiclesdesigned for specific, commercial purposes), such as semi-tractortrailers, buses, and the like, may include towing, braking, and camerasystems. However, these vehicles either integrate these systems in theiroriginal, manufactured state or accommodate these systems throughspecialized and often expensive components and features (usually sold bythe manufacturer) that are unique to the specialized vehicle and cannotbe easily adapted for use on general purpose vehicles. Few—ifany—general purpose vehicles (i.e., vehicles designed for massproduction and sale without any anticipated, narrow commercial use),such as sedans, station wagons, cross-over vehicles, compact cars,subcompact cars, sport utility vehicles (SUVs), general purpose pick uptrucks, mini-vans, and the like, are designed to accommodate specializedsystems of this nature or, to the extent that general purpose vehiclesmay have towing, cargo, and other accessory systems, these systems areintegrated and closed as described above.

Finally, many existing systems—whether integrated or after-market—merelyprovide passive feedback that is specific to that system. For example,tire pressure-monitoring systems (TPMS) on trailers, when sensing afault condition, might only display a warning light for the driver. Tothe extent that trailer also has a brake controller and sway module,these systems would not be automatically alerted to the potential tireproblem. Instead, they would merely sense additional faults—ifany—caused by the tire problem on an individual basis and displayseparate warnings (or possibly take independent action specific to thatsystem only). Ultimately, the root cause of these disparate warningswould only be realized to the extent the driver/end user recognized thatthese independent warnings were, in fact, interconnected. Furthermore,and especially to the extent each of the systems merely displays apassive warning indicator, additional driver/end user intervention wouldbe required. In short, after-market systems capable of generating usefuldata are compartmentalized and restricted to a specific purpose.

In view of the limitations of existing, integrated and/or passivevehicle diagnostic systems, a need exists for systems and methods thatcollect, process, and further leverage data provided by any number ofvehicle accessories selected by the driver/end user to accomplish tasksdesired by and more useful to the driver/end user, rather than focusingonly on those deemed appropriate by the vehicle manufacturer. Further, adevice, method, and system that allows for active communication,interconnection, and control of vehicle accessories systems would bewelcome, especially in the area of trailer controls for actions such asbraking, controlling unwanted motion, breakaway, and the like. Inparticular, systems which integrate different components (i.e.,discrete, after-market devices or modules dedicated to performing aparticular function, such as trailer braking, tire pressure monitoring,cargo carrying, etc.) so that they can communicate with each other andmake decisions and verify on collective information (which is nototherwise available, directly or indirectly, to individual componentsdue to their inability to share information) in manner that allows forpartially or fully automatic functions would advantageous.

SUMMARY

The present disclosure includes a system, method, and devices related todata collection and communication of the performance of various vehicleaccessories and systems. These accessories and systems are described ingreater detail below, and any combination of elements and/or methods arecontemplated as aspects and embodiments of the overall invention.

One embodiment of the invention comprises a system having anycombination of the following features:

-   -   at least one towing accessory device;    -   a sensor operatively coupled with the towing accessory device;    -   a controller in operative communication with at least one of the        sensor and the towing accessory device to receive data with        respect to the towing accessory device and wherein the        controller processes the data and sends a direction to act to        the towing accessory device;    -   wherein the controller comprises a communication device in        operative communication with the sensor to receive and transmit        data with respect to the towing accessory device and an        electronic storage device in operative communication with at        least one of the following: the sensor and the communication        device;    -   wherein the direction to act is sent via the communication        device to the towing accessory; a user interface in operative        communication with at least one of the communication device and        the electronic storage device;    -   wherein the user interface includes at least one of a        smartphone, tablet, computer, and user interface of a trailer        brake controller;    -   wherein the at least one towing accessory device consists of at        least one of the following: brake controller, break away device,        trailer signal converter, sway control device, tire pressure        monitoring system, camera, trailer brakes, fifth wheel hitch,        coupler, gooseneck coupler, hitch bar, hitch ball mount, pin        box, weight distribution system, jack, ramp, roof rack, cargo        securing system, cargo carrier and winch.    -   wherein the at least one towing accessory device comprises first        and second towing accessory devices whereby the first towing        accessory device includes the sensor and the second towing        accessory devices includes a second sensor operatively coupled        thereto;    -   wherein the controller receives second data from the second        sensor and processes the second data and sends a direction to        act to the first towing accessory device; and    -   a second sensor coupled with the towing accessory device.

A separate embodiment is directed to a system having any combination ofthe following features:

-   -   at least one towing accessory device;    -   a sensor operatively coupled with the at least one towing        accessory device;    -   an electronic storage device in operative communication with the        sensor, the electronic storage device receiving data from the        sensor wherein the electronic storage device processes the data        and sends a direction to act to the at least one accessory        device;    -   a user interface in operative communication with the sensor and        the electronic storage device;    -   a communication device in operative communication with any        combination of: the at least one towing accessory device, the        sensor, the electronic storage device, the user interface, an        internet-based data server, and a private party data server;    -   wherein the sensor includes a transceiver to send and receive        the data and the direction to act;    -   wherein the sensor, electronic storage device and user interface        communicate via a wireless communication platform;    -   wherein the wireless communication platform includes at least        one of Bluetooth and Wi-Fi;    -   wherein the at least one towing accessory device includes first        and second towing accessory devices, the first towing accessory        device comprising the sensor and the second towing accessory        device comprises a second sensor;    -   wherein the first sensor generates and sends the data to the        electronic storage device and the electronic storage device        sends instructions to the second towing device to take a second        action;    -   wherein the second action is to prevent operation of the second        towing accessory device; wherein the second sensor sends second        data to the electronic storage device confirming at least one        of: the direction to act and the second action is/are complete;    -   wherein additional data is communicated to the electronic        storage device through the user interface; and    -   wherein the user interface comprises a trailer brake controller.

Yet another embodiment contemplates a system having any combination ofthe following features:

-   -   a first towing accessory device comprising a first sensor;    -   a second towing accessory device comprising a second sensor, the        first and second towing accessory devices in operative        communication; and    -   a communication device in operative communication with the first        and second sensors, wherein data from the first sensor is        communicated to the communication device and the communication        device sends instructions to the second sensor to generate an        action for the second towing accessory device;    -   wherein the communication device includes at least one of a        smartphone, tablet, computer, and device with a processor;    -   further comprising a user interface in operative communication        with the communication device;    -   wherein the user interface and communication device are a single        device; and    -   further comprising a third towing accessory device comprising a        third sensing device, wherein the third sensor is in operative        communication with the first and second sensors, whereby the        communication device sends instructions to the third sensor to        generate an action for the third towing accessory device.

A still further embodiment contemplates a system having any combinationof the following features:

-   -   a first towing accessory device comprising a first sensing        device;    -   a second towing accessory device comprising a second sensing        device, the first and second sensing devices in operative        communication, wherein the first sensing device provides data to        the second sensing device generating an action by the second        towing accessory device;    -   wherein the second sensing device comprises a microprocessor;    -   wherein the microprocessor includes a wireless transceiver;    -   further comprising an electronic storage device, wherein the        first and second sensing devices send operative data, optionally        including data provided by the first sensing device to the        second sensing device, wirelessly to the electronic storage        device and the electronic storage device sends operative        instructions to at least one of the first and second sensing        devices to generate at least one act by at least one of the        first and second towing accessory devices; and    -   further comprising a user interface wherein the user interface        sends user data to the electronic storage device, wherein the        user data is used by at least one of the first and second towing        accessory devices in performing the at least one act.

The foregoing embodiments are merely exemplary of some of the aspects ofthe system. Additional features and elements may be contemplated anddescribed herein. Also, features from one of the foregoing embodimentsmay be combined with features from any of the other foregoingembodiments.

DESCRIPTION OF THE DRAWINGS

FIG. 1 is a schematic side view of an embodiment of the data collectionand communication system of the present disclosure;

FIG. 2 is a schematic perspective view of embodiments of the datacollection and communication system of the present disclosure applied toa towed vehicle and a towing vehicle;

FIG. 3 is a perspective view of a fifth wheel hitch module of the datacollection and communication system of the present disclosure;

FIG. 4 is a perspective view of a gooseneck coupler module of the datacollection and communication system of the present disclosure;

FIG. 5 is a perspective view of a coupler module of the data collectionand communication system of the present disclosure;

FIG. 6 is a schematic perspective view of various modules of the datacollection and communication system of the present disclosure applied toa towed vehicle and a towing vehicle;

FIG. 7 is a perspective view of a weight distribution modules of thedata collection and communication system of the present disclosure;

FIG. 8 illustrates various plan views of display screenshots associatedwith a brake controller modules of the data collection and communicationsystem of the present disclosure;

FIG. 9 is a flowchart indicating electromechanical interactions betweenthe trailer brake controller (TBC), the jack, and possibly othercomponents of the invention according to certain embodimentscontemplated herein;

FIG. 10 is a flowchart indicating interactions between the trailer brakecontroller (TBC), the trailer brakes (TB), and possibly other componentsof the invention according to certain embodiments contemplated herein;

FIG. 11 is a flowchart indicating user data interactions between thecommunications (COMM DEV) and possibly other components of the inventionaccording to certain embodiments contemplated herein;

FIG. 12 is a flowchart indicating interactions between the trailer brakecontroller (TBC), the fifth wheel hitch (5^(th) Wheel), the jack, thecommunications device, the information storage device, and possiblyother components of the invention according to certain embodimentscontemplated herein;

FIGS. 13A through 13C is a flowchart indicating interactions between thetrailer brake controller (TBC), the trailer brakes (TB), thecommunications device, and possibly other components of the inventionaccording to certain embodiments contemplated herein; and

FIG. 14 is a schematic plan view of how a discrete component in theinventive system accomplishes certain functions according to theembodiments of the invention contemplated herein.

DETAILED DESCRIPTION

Reference will now be made in detail to exemplary embodiments of thepresent invention, examples of which are illustrated in the accompanyingdrawings. It is to be understood that other embodiments may be utilizedand structural and functional changes may be made without departing fromthe respective scope of the invention. Moreover, features of the variousembodiments may be combined or altered without departing from the scopeof the invention. As such, the following description is presented by wayof illustration only and should not limit in any way the variousalternatives and modifications that may be made to the illustratedembodiments and still be within the spirit and scope of the invention.

As used herein, the words “example” and “exemplary” mean an instance, orillustration. The words “example” or “exemplary” do not indicate a keyor preferred aspect or embodiment. The word “or” is intended to beinclusive rather an exclusive, unless context suggests otherwise. As anexample, the phrase “A employs B or C,” includes any inclusivepermutation (e.g., A employs B; A employs C; or A employs both B and C).As another matter, the articles “a” and “an” are generally intended tomean “one or more” unless context suggest otherwise.

Overview

As a preliminary matter, the external components of the invention may beclassified as electronics, connection devices, accessory, systems,interface/ancillary systems, and a master control device. These unitsmay constitute individual, add-ons for consumer vehicle installations;however, the components of the present system are necessarily engineeredwith common features, such as intra-component communication protocols,power systems, standardized inputs and outputs, and the like, tofacilitate operation of the system. In the same manner, certaincomponents must sense, generate, or receive data that was not accessibleto individual components in past stand-alone installations.

As noted above, individual devices, modules, and units—and particularlythose commonly sold as stand-alone, after-mark additions to towing,cargo carrying, and other accessory systems—comprising the presentsystem are referred to as components. Each component includes anyappropriate functional hardware (i.e., the physical structure associatedwith the intended functionality of the component itself; for example, ina hitch bar, the actual structural member that engages the receiverhitch and/or, in a ramp, the planar sheet attaching to the vehicle bedfor movement of cargo over it) and a power supply, such as an on-boardbattery or connector for receiving power from another source. The powersupply provides electricity to any sensors and output controls needed bythat component, as well as its communications equipment to send andreceive data to/from other devices, a cloud or other externalinformation storage, and various computing device, including personaldevice and/or those associated with the vehicle itself (i.e., itscommunications bus) via wired or wireless connections, any appropriatefunctional hardware (i.e., the physical structure associated with theintended functionality of the component itself; for example, in a hitchbar, the actual structural member that engages the receiver hitchand/or, in a ramp, the planar sheet attaching to the vehicle bed formovement of cargo over it), and microcontroller (or other, similarcircuitry). Some components may also include an optional userinput/interface. Appropriate wiring, dedicated circuitry, and other,similar connections will be provided within the housing of the componentto ensure delivery of electricity and signals as appropriate to thecomponent.

Separately, it will be understood that the system may be describedaccording to the functionality and utility it provides. That is, thehardware in the system (without reference to specific components) mustbe configured to accomplish specific functions. For example, the systemmust be able to sense data (whether from automated sensors,user-provided inputs, or from external resources such as the internet orcloud storage), to store data, to communicate with components in thesystem, to communicate with devices external to the system (usually viawireless connectivity to the internet and internet-based services, cloudand other data storage services, and/or directly to third party dataservers), to interface with and provide feedback to the end user, toevaluate, process, prioritize, and leverage data, and to coordinate bothcomponent and system-wide actions in response to data and inputs by wayof outputs. Many of these functions were not previously used or fullyleveraged in past vehicle accessory systems. Software, microprocessors,integrated circuitry, programmable logic controllers, and/or the use ofother, dedicated devices enable these functions.

In this context, “logic” refers to any information and/or data that maybe applied to direct the operation of a processor. Logic may be formedfrom instruction signals stored in a memory (e.g., a non-transitorymemory). Software is one example of logic. In another aspect, logic mayinclude hardware, alone or in combination with software. For instance,logic may include digital and/or analog hardware circuits, such ashardware circuits comprising logical gates (e.g., AND, OR, XOR, NAND,NOR, and other logical operations). Furthermore, logic may be programmedand/or include aspects of various devices and is not limited to a singledevice. Furthermore, the terms “user,” “customer,” “consumer,” and thelike are employed interchangeably throughout the subject specification,unless context suggests otherwise or warrants a particular distinctionamong the terms. It is noted that such terms may refer to human entitiesor automated components supported through artificial intelligence (e.g.,a capacity to make inference). As such, embodiments may describe a useraction may not require human action.

Also, throughout this disclosure, aspects of the invention may bedefined according to individual components and/or according to thedesired functionality of the system. As noted above, one component maydeliver multiple functions and/or several components may redundantlyperform and verify certain functions within the system. Therefore,attention should be given to the context of the disclosure with respectto both the components and the functionality of the system to affordthis disclosure its broadest reasonable meanings.

Electronics components for use in the system contribute to the activemanagement and control aspects of the system. They may include brakecontrollers and trailer braking systems, anti-sway attachments,converters, trailer breakaway systems, tire pressure monitoring systemsfor trailers and other attachments (i.e., separate and distinct fromsuch systems integrated into the on-board electronics of the vehicleitself), and external cameras (i.e., also separate and distinct fromon-board systems integrated with the vehicle itself).

Connection devices assist in establishing and maintaining the connectionbetween the towed objects (e.g., vehicle to vehicle, vehicle to trailer,trailer to trailer, etc.). They may include fifth wheel and gooseneckassemblies, pin boxes, coupling systems, weight distribution mechanisms,hitches, and hitch bars.

Accessory systems are a general class of components accomplishing tasksthat may not be directly related to towing. This range of devices mayinclude jacks and lifting/support mechanisms, roof top and hitch-basedcargo carriers, roof racks, assemblies and systems for securing items tothe vehicle, ramps, and winches and other cable/wire dispensing andretracting devices.

Interface and ancillary systems include communication devices,information storage devices, and non-vehicle based batteries and powersystems. Generally speaking, all of these items effectively support thefunctionality of the present system.

A master control or controller may coordinate functioning of the presentsystem. It may include or rely on: a) existing equipment installed bythe original manufacturer, b) a separate device specifically designed tointegrated the various other components (i.e., one or more of theelectrical components, connection devices, accessory systems, and/orinterface/ancillary systems), or c) specifically designed features orhardware provided to a plurality of the “various other components” toimpart overall control functionality to the present system (i.e., adistributed, networked function provided by a combination of componentsin the system). The master control may include any number of userinterface devices (e.g., touch screen, keyboard and display,voice-activated control including a microphone, audio speakers,functional buttons, etc.), that may be incorporated within the mastercontrol unit itself or coupled (e.g., wired or wirelessly) to thecontrol unit as part of a separate component or independent user device(e.g., a mobile phone, tablet, personal computing device, etc.). It isnoted that these user interface devices may also be provided separatelyon any of the other system components.

Inputs provided to the present system may be generated from any of theaforementioned components or by leveraging existent aspects of thevehicle and/or trailer/towed product. Examples of the types of inputsthat may be useful in the invention are listed below, although thedescription for the inputs provided in this section are within thecontext of the vehicle accessory system field and may be supplemented orotherwise understood to entail additional aspects by those of skill inthe art. Any component disclosed in this specification may have anycombination of the following inputs:

-   -   1) Anti-lock braking system (ABS);    -   2) Active/inactive;    -   3) Actuate: indicative of movement of any of the components any        direction;    -   4) Air ride: pin box pressure;    -   5) Angle (may also be referred to as articulation): the angular        measurement between a trailer (or component associated with the        trailer) and the tow vehicle itself;    -   6) Auto dimming;    -   7) Auto inflate;    -   8) Biometrics;    -   9) Boost;    -   10) Brake intent: quantitative information indicative of the        intent or intensity with which the brakes may be applied;    -   11) Brake output;    -   12) Charging status;    -   13) Collision sensor: particularly after any such event;    -   14) Connect/disconnect;    -   15) Crash detection: particularly prior to any such event;    -   16) Current voltage;    -   17) Deceleration/acceleration;    -   18) Default: to the extent the component has or may be provided        with such a setting;    -   19) Effort: expressed as a percent of usage for the component in        question;    -   20) Engagement (mechanical);    -   21) “Electric Over Hydraulic” (EOH)/electric mode: indicative of        whether electric or hydraulic systems are employed, particularly        with respect to braking;    -   22) Faults;    -   23) Gain: setting which limits the output voltage to just below        a setting where the wheels would lock;    -   24) Heat;    -   25) High pin: as used herein, “high pinning” means that the        component is not engaged;    -   26) Image;    -   27) Lamp type;    -   28) Lane change;    -   29) Level;    -   30) Load;    -   31) Location: particularly with respect to the Global        Positioning System (GPS);    -   32) Lube;    -   33) Noise: both in an audible and electrical context;    -   34) Operational frequency;    -   35) Power loss;    -   36) Pressure: as appropriate to the component, including air        pressure and/or hydraulic pressure;    -   37) Proximity: with respect to one external component's physical        location in comparison to another external component (or some        other reference point);    -   38) Pulse Width Modulation (PWM)/multiplex;    -   39) Second lock/latch: as may be appropriate to certain external        components, such as fifth wheel and other connections system        components;    -   40) Status: within the context of a particular variable;    -   41) Vertical deceleration;    -   42) Warning;    -   43) Wear;    -   44) Wheel speed: as measured by various methods, such as a        rotation sensor, direct current voltage generator, a hall        sensor, outputting pulses, etc.

Outputs provided by system components are specifically generated by thecomponents based on inputs, sensed or user-provided data (as describedherein), or some combination thereof. To the extent a componentincorporates certain sensors (e.g., accelerometers, thermistors,thermocouples, pressure transducers, gyroscopes, etc.) or dataprocessors (e.g., microprocessors, dedicated circuitry, etc.), certaininformation may be created by the component, although this “sensed data”should be treated separately. The outputs may be communicated andutilized within the present system to produce a desired end result(e.g., coordinated warnings to the end user, improved braking function,an overall improvement to the end user's experience, etc.). Thus, theoutputs identified below are representative of at least some of thetypes of information that might be communicated among the components ofthe present system. The descriptive information noted above for theinputs also applies to the similarly named outputs in the list below.Any component disclosed in this specification may have any combinationof the following outputs or various other outputs:

-   -   1) Anti-lock braking system (ABS);    -   2) Active/Inactive;    -   3) Actuate: movement of the component in question;    -   4) Air ride: pin box pressure;    -   5) Angle (may also be referred to as articulation): the angular        measurement between a trailer (or component associated with the        trailer) and the tow vehicle itself;    -   6) Auto dimming;    -   7) Auto inflate;    -   8) Biometrics;    -   9) Boost;    -   10) Brake intent: quantitative information indicative of the        intent or intensity with which the brakes may be applied;    -   11) Brake output;    -   12) Charging status;    -   13) Collision sensor: particularly after any such event;    -   14) Connect/disconnect;    -   15) Crash detection: particularly prior to any such event;    -   16) Current voltage;    -   17) Deceleration/acceleration;    -   18) Default: to the extent the component has or may be provided        with such a setting;    -   19) Effort: expressed as a percent of usage for the component in        question;    -   20) Engagement (mechanical);    -   21) “Electric Over Hydraulic” (EOH)/electric mode: indicative of        whether electric or hydraulic systems are employed, particularly        with respect to braking;    -   22) Faults;    -   23) Gain: setting which limits the output voltage to just below        a setting where the wheels would lock;    -   24) Heat;    -   25) High pin: as used herein, “high pinning” means that the        component is not engaged;    -   26) Image;    -   27) Lamp type;    -   28) Lane change;    -   29) Level;    -   30) Load;    -   31) Location: particularly with respect to the Global        Positioning System (GPS);    -   32) Lube;    -   33) Noise: both in an audible and electrical context;    -   34) Operational frequency;    -   35) Power loss;    -   36) Pressure: as appropriate to the component, including air        pressure and/or hydraulic pressure;    -   37) Proximity: with respect to one external component's physical        location in comparison to another external component (or some        other reference point);    -   38) Pulse Width Modulation (PWM)/multiplex;    -   39) Second lock/latch: as may be appropriate to certain external        components, such as fifth wheel and other connections system        components;    -   40) Status: within the context of a particular variable;    -   41) Vertical deceleration;    -   42) Warning;    -   43) Wear;    -   44) Wheel speed: as measured by various methods, such as a        rotation sensor, direct current voltage generator, a hall        sensor, outputting pulses, etc.

The inputs and outputs above may comprise data. This data may begenerated, recorded, and transmitted according to conventional means,including both digital and analog means. The data may be shared amongsome or all of the components in the system, either in its original formor after undergoing further processing (e.g., prioritization, selection,calculation of additional variables/values, averaging, etc.). Also, asfurther described below, the generation of data may be accomplished by avariety of sensors or input mechanisms and the recordation of the datais preferably via electrical or electromechanical means, while itstransmission (both within the system and to components outside of it)may be by wire or wireless means. In addition to being classified asinputs or outputs described above, data may also be further classifiedas sensed data, user input data, and web-based data (which includes datadrawn from the internet, remote cloud-based services, third partyservers, and/or receipt of previously transmitted data from the presentsystem that has undergone further analysis/processing via computingdevices that are external to the system).

Sensed data may be produced by sensors or detectors integrated into anygiven system component, as well as data created by sensors associatedwith the vehicle or the towed product. Sensed data may includeinformation that is sensed/detected by a component and/or inputsreceived from other components that have been further processed. Ineither case, the sensed data may be stored within a memory unit of thecomponent in question and/or stored with dedicated components within thesystem. If sensed data effectively acts as an input or output, it may beencompassed by any of the categories and definitions provided above.

Similarly, data provided by a user (e.g., via a graphical user interfaceon one or more of the system components or via an application, sensor,and/or input means associated with an external user device (or as partof the system, e.g., the trailer brake controller), such as a mobilephone, tablet, or personal computing device) may also encompass theinputs or outputs as described above/herein. In these cases, thecomponent will be programmed to query the user with respect to aparticular parameter or variable (e.g., entries might range from basicuser profiles for associating preferred default settings and logginginformation all the way to allowing the user to set significantvariables, such as gain, trailer weight, etc.). These user-derivedinputs can then be stored, used to compute additional values/variables,shared, and leveraged throughout the wider system. For example, suchvalues might serve as a comparison points or allow for verification ofother sensed data and/or calculated values automatically produced by thesystem.

As yet another distinction, certain components of the system may haveinternet-capabilities. That is, by way of wired or wireless dataconnections to a network (e.g., Ethernet, Wi-Fi, cellular network,etc.), it may be possible for components to be programmed to accessspecific data or information stored on servers and other computingdevices, referred to herein as web-based data. In some embodiments, thenature of the data connection could even serve as a layer of privacy anddata protection. For example, while the components of the system mayrely on a wireless local area network associated with the vehicle or aspecific component in the system (e.g., the communications device, themaster controller, etc.), transmission of web-based data would onlyoccur via a wired connection from a selected component. In this manner,it would become more difficult for an unauthorized party to access allof the components in the system and, further, by requiring internetconnectivity via a wired connection, access to the system could beselectively limited by the user by simply unplugging a cord from thecomponent in question. Moreover, the entire system may act as a closedloop system, whereby the individual components send and receive dataamongst themselves without intervention of a separate device. This maybe referred to as a mesh-network.

This approach may have several advantages. First, such web-based datamay be independently verified and updated by third party experts,including manufacturers, weather forecasters, transit authorities, andthe like. Second, it provides an opportunity to update componentsoftware or firmware, thereby enhancing the overall functionality of thesystem. For example, web-based data may come in the form of updates andreceipt of data and information that may have only come into existenceafter the component is manufactured and/or after the end user purchasedand installed the component. Web-based data such as weather forecasts,location, and traffic status may even be leveraged to (e.g., viamodifications to calculations for braking) anticipate and/or plan inadvance for certain conditions, as well as to assist the end user andthe system itself to act in real-time in response to the implications ofthe data. Finally, web-based data may allow storing data from thepresent system, including user inputs (e.g., user profiles, etc.) andsensed data (e.g., use or event logs, system performance, etc.), forsubsequent retrieval via cloud-based computing or other, similar datastorage. Such web-based data may be compared against inputs and senseddata from a number of components in order to establish system norms, toverify the plausibility of data and calculations associated with thesystem, and/or contribute to the web-based data standards themselves),identify exceptions, and send messages (including warnings, cautions,reminders, and status updates). Web-based data also enables the abilityto update the software or firmware of the components of the system.

The distinctions between sensed data, user-input data, and web-baseddata are not intended as rigid distinctions. As an example, data may besensed by a component and subsequently transmitted via an internetconnection. In the same manner user-input data may come into existencebased upon an observation or read-out the user obtained from theinternet and/or from a sensor/readout provided by a component. In theseand other cases, the categories of sensed data, user-input data, andweb-based data are informative in their nature and should not beunderstood as limiting how the data is used and/or how the system mayoperate. Depending upon context, a reference to data herein mayencompass any of these categories.

While embodiments may refer to a particular network (e.g., internet,cloud-storage, cellular network, etc.), it is noted that a network maycomprise various other configurations. For instance, a network typicallyincludes a plurality of elements that host logic. In packet-basedwide-area networks (WAN), servers (e.g., devices comprising logic) maybe placed at different points on the network. Servers may communicatewith other devices and/or databases. In another aspect, a server mayprovide access to a user account. The “user account” includes attributesfor a particular user and commonly include a unique identifier (ID)associated with the user. The ID may be associated with a particularmobile device, devices associated with a user, and/or active vehicleaccessory system. The user account may also include information such asrelationships with application usage, location, personal settings, andother information. In some embodiments, the ID may be combined withbiometric data and/or used for crosschecking, data logging/archivalpurposes, theft deterrence, and other purposes described herein.

Each component may create, store, and process data (e.g., sensed,user-input, web-based, cloud server based, as stored, and/or aftercomputations), as well as receive inputs and produce outputs. It will beunderstood that the outputs from any one component may serve as inputsfor another. Similarly, each component identified herein may employcombinations of selected inputs and outputs, as will be described forcertain embodiments below. Although a number of components may useidentical inputs and/or produce identical outputs, the fact thatmultiple components produce the same feedback to the user (e.g., a lowpressure warning, a disconnection warning, etc.) will benefit thedriver/end user by delivering coordinated messages across multipledisplays/interfaces, instead of separate and possibly differentlypresented feedback based on the individual component's settings. Asnoted below, the system may also make certain determinations aboutand/or corrections to identical or similar data generated or otherwiseflowing through the system (e.g., multiple data inputs may allow for“cross-checking” across the entire system).

In the same manner, a number of components may provide similar orredundant functions (e.g., ability to receive user-inputs, data storage,communications capabilities, etc.). The disclosure of these functions isnot intended to be exclusive to a single component. Moreover, it will beunderstood that all of the functionality of a particular component couldbe subsumed by a separate component. Also, redundant functionality maygive rise to redundant inputs and data, which can then be crosscheckedand further processed as noted herein.

The components of the present system communicate with one another, viawired and/or wireless connections and/or protocols, although wirelessinstallations present certain advantages. As described below (includingthe Examples), wireless connections may allow for easy integration ofnew components. Retrofitting of existing, non-wireless products may beaccomplished through use of an adapter or series of adapters. Theseadapters would be affixed proximate to the component of interest andestablish a connection with that component via its conventional means(e.g., a wired connections such as USB cables, dedicated wires, coaxialcables, optical fiber cables, twisted pair cable, Ethernet HDMI, and thelike). The adapter would possess sufficient circuitry to communicatewith the system (receive inputs to provide to the component and transmitappropriate outputs based on data provided by the component) and mayalso incorporate additional sensors/functionality as appropriate to thatcomponent.

Adaptor may refer to a wireless adapter that allows an existing orlegacy component to communicate wirelessly with other components of asystem. For instance, an adaptor may couple to a wired connection of adevice and may comprise a transmitter, sensor and/or receiver (or asingle device that combines all of these components) that operativelysends and/or receives data. It is noted that at least one embodiment mayutilize components that are in communication while other components arenot. In an example, a user may utilize a brake controller and a swaycontroller that are in wireless communication with each other, while acamera system is not in communication with the controller or swaycontroller.

Adapters may also refer to an identification tag such as a radiofrequency identification (RFID) tag, or other wireless identificationtag (passive or active). An identification tag may be attached to ordisposed within a component via an adhesive, over molding, mechanicalcoupling, magnetic coupling, or the like. For instance, an RFID tag canbe adhered to a steel component (e.g., ball hitch, or the like). TheRFID tag may be preprogrammed to store identification for the specificcomponent and/or may be programed by a user (e.g., end user, installer,etc.) to identify the particular component by make, model,characteristics (e.g., maximum load capacity, etc.). A component of thedisclosed system may generate a signal that elicits a response from theidentification tag. For instance, a master control may generate a signalto communicate with the identification tag. The master control may thenreceive a response and may store received information. In anotherexample, a user device (e.g., smart phone) may communicate with theidentification tag. The user device may then communicate with a mastercontrol. Separate sensors on or in any component (including the mastercontroller and/or the component to which the adapter RFID tag isadhered) may be used to monitor and further process the signal producedby the tag, such as for purposes of monitoring displacement or movementof the tag, relative positioning of a plurality of tags, and the like.

The protocols inherent to wireless communication between systemcomponents may encompass any known system. For instance, embodiments mayutilize various radio access network (RAN), e.g., Wi-Fi, Wi-Fi direct,global system for mobile communications, universal mobiletelecommunications systems, worldwide interoperability for microwaveaccess, enhanced general packet radio service, third generationpartnership project long term evolution (3G LTE), fourth generation longterm evolution (4G LTE), third generation partnership project 2,BLUETOOTH®, ultra mobile broadband, high speed packet access, xthgeneration long term evolution, or another IEEE 802.XX technology.BLUETOOTH (in any of its various iterations), various wirelesstechnologies for exchanging data over short distances (e.g., ZigBee,RuBee, DASH7, etc.), and other protocols and personal area networks areexpected to have particular utility. In the same manner, wirelesscommunication may also include, in whole or in part, communicationstransmitted over more traditional local area network (including suchnetworks provided by the vehicle and/or trailer/towed product) or acellular data networks, so as to incorporate aspects of cloud-basedcomputing systems, information available via world wide web and otherinternet connectivity, and the like. As such, any indication of“wireless,” “Wi-Fi,” or other similar terminology should be readexpansively (at least within the context it is used) throughout thisdisclosure. Moreover, embodiments may use one or more differentcommunications protocols or devices (whether wired or wireless) tocommunicate between the various components of the system.

The components of the system may rely on any of the following sensors.These sensors are integrated with the power supply, wiring, and/or otheroperational aspects of the component in question. Exemplary sensorsinclude, but are not limited to the following (any type of sensor may beutilized without departing from the present teachings):

-   -   Load sensors. These devices indicate the application of force        along a planar surface of the sensor. They may be incorporated        at discrete locations and at various orientations to determine        deliberate activation or unexpected/unintended scenarios.        Examples where such sensors may be positioned include in        conjunction with other sensors identified herein.    -   Accelerometers/decelerometers and motion/movement detection        sensors: These devices may include micro electromechanical        systems (MEMS), micro-opto-electromechanical systems, and other,        similar types of acceleration measuring devices.    -   Temperature sensing devices: These may include thermistors,        thermocouples, thermometers, and other similar instruments, also        including those optionally incorporated onto/with integrated        circuits (ICs).    -   Wheel speed sensors: These devices include Hall Effect sensors,        accelerometers, gyroscopes, and the like. These can be also used        to detect ABS.    -   Speed and distance sensors: These may include GPS, radar, and        other known technologies.    -   Tire pressure monitors: These devices use one or more pressure        transducers with thermistors for temperature measurement, as        well as an accelerometer to allow for speed measurement. Insofar        as pressure and temperature of gas are related, the sensor may        automatically adjust as appropriate to deliver accurate        data/outputs.    -   Current sensors: These devices measure load current according to        well-known principles. As an example, a linear Hall effect        sensor can to detect current in automobile or Trailer lamps        without the use of a shunt resistor to sense the current,        resulting in the non-contact measurement of current (ZCI).    -   “Sleep” Devices: These items are associated with any of the        sensors or integrated means to cause the sensor/means to wake up        after sensing certain activity to reduce power consumption of        the larger sensor/component. They may comprise a single        accelerometer or simple motion-activated device that generates a        signal to activate a wider array of devices/sensors for a        pre-determined period of time or other set of conditions (e.g.,        until motion stops), although other common approaches to detect        a “wakening” state are possible (e.g., via current or voltage        sensing, proximity of an object, user-initiated action, signals        from other components, etc.).    -   Voltage monitors: These devices may detect low battery voltage,        high battery voltage and other adjustments based on battery        voltage according to well-known principles. Analog to digital        converter (ADC) in a microcontroller or a voltage comparator are        particularly well suited to serve as such sensors.    -   Frequency to voltage converters: These devices sense frequencies        and convert them to a voltage-based signal according to        well-known principles.    -   Proximity sensors: These devices rely on distance or range        finders, including lasers and infrared sensors, to measure        distance between the sensor and some other tangible object.    -   Angular sensors: The devices may include gyroscopes,        accelerometers, anisotropic and other magnetoresistive sensors,        potentiometers, inductive or capacitive, Hall, optical encoders        to detect sway, angle between towed and towing vehicle, mounting        angle of device, level sensing, etc.    -   Cameras: Relying upon appropriate software, these may sense        angle, proximity, distance, lane change, patterns, faces, etc.        These devices may also include more simplistic optical sensors,        such as light intensity detectors associated with ambient or        specifically designed light sources. Depending upon context,        camera may refer to a sensor built into a particular component        and/or to the discrete camera component described in the        Electronics Systems section below.    -   Touch sensors: These devices use resistive, inductive or        capacitive mechanisms to indicate contact.    -   Location sensors: Global Positioning System (GPS) and other        similar technologies may be employed to detect location.    -   Crash sensors: These devices rely on accelerometers to detect        sudden impact like crash, similar to those used in vehicle        airbag deployment.    -   Load cells, strain gages, deflection sensors: These devices are        well-known means of measuring weight/mass or other forces        exerted in a particular direction.    -   Pressure transducers: These devices operate according to        well-known principles to detect fluid pressure (e.g., brake        fluid, air, etc.) to sense braking effort, pedal pressure, fluid        exertion, etc.

Additionally, in certain embodiments, one component will serve as themaster control by and, for the most part, through which the presentsystem operates. In many embodiments, this master control may beintegrated into a component, with the trailer brake controller being apotential choice owing to its existing familiarity with drivers and endusers. Such trailer brake controllers often include graphic userinterfaces, making them easily adaptable for further use as a mastersystem control. Additionally, brake controllers are often located withinthe vehicle to streamline the delivery of warnings, updates, and othersystem information.

To the extent a separate component is provided for the master control,it should be in the vicinity and/or field of vision of the driver orintended user. It preferably includes functions for user interface anddisplay (including input/output connections and functionality), wirelesscommunication, information storage, and computation/microprocessorcapabilities.

Alternatively, the master control could be integrated in or across anynumber of the other system components. It may be provided as a softwarepackage or application for an existing consumer-computing device, suchas a laptop, digital assistant, tablet, or other electronic devicepossessing sufficient computing power and wireless and graphical/otheruser interface capabilities. In yet a further alternative, the mastercontrol could be produced as a standalone component, such as applicationthat may be installed on user device or user equipment, therebyenhancing overall end user experience with a dedicated, speciallydesigned interface that is convenient and simple to install. Furtherstill, the system may not utilize a master control, but instead willshare the control aspect among each of the various components. “Userequipment,” “device,” “user equipment device,” “client,” and the likeare utilized interchangeably in the subject application, unless contextwarrants particular distinction(s) among the terms. By way of example,user equipment may comprise an electronic device capable of wirelesslysending and receiving data. A user equipment device may have aprocessor, a memory, a transceiver, an input, and an output. Examples ofsuch devices include cellular telephones (e.g., smart phones), personaldigital assistants (PDAs), portable computers, tablet computers(tablets), hand held gaming counsels, wearables (e.g., smart watches),desktop computers, global positioning system (GPS) devices, and otherdevices possessing sufficient processing and software capabilities.

The master control can cross check data that is produced or gathered bythe larger system. In particular, certain system components may producesimilar or comparable forms of data (e.g., similar sensors on differentdevices, user inputs and web-based data relating to the same variable,etc.). In these scenarios, the master control can be specificallyprogrammed to analyze such comparable data and determine the final orcorrected value, which is then shared with all components in the system.This comparative function may also be useful in creating troubleshootingregimens in which user inputs are compared against sensed data and/orweb-based information, with the master control then providing feedbackand suggestions to the end user.

Any final or corrected values determined by cross-checking could beaveraged from all the available data, or the master control might selectone or more values based on pre-programmed hierarchy indicating aparticular component provides more reliable information with respect tocertain variables in comparison to other components (e.g., a wheel speedsensor located on the trailer may be deemed a more reliable indicator oftrailer movement than an accelerometer located in the connection deviceassociated with that trailer). In this regard, individual components mayalso be programmed with similar “cross-checking” capability to theextent they incorporate sensors or receive inputs for comparable butconflicting data.

In an aspect, the master control (as well as other components) mayutilize high level processing techniques, such as artificialintelligence, statistical models, or other processes and/or algorithms.These high level-processing techniques can make suggestions, providefeedback, or provide other aspects. In embodiments, master control mayutilize classifiers that map an attribute vector to a confidence thatthe attribute belongs to a class. For instance, master control may inputattribute vector, x=(x1, x2, x3, x4, xn) mapped tof(x)=confidence(class). Such classification can employ a probabilisticand/or statistical based analysis (e.g., factoring into the analysisaffinities and ingredient attributes) to infer suggestions and/ordesired actions. In various embodiments, master control may utilizeother directed and undirected model classification approaches include,e.g., naïve Bayes, Bayesian networks, decision trees, neural networks,fuzzy logic models, and probabilistic classification models providingdifferent patterns of independence. Classification may also includestatistical regression that is utilized to develop models of priority.Further still, classification may also include data derived from anothersystem, such as automotive systems.

In accordance with various aspects, some embodiments may employclassifiers that are explicitly trained (e.g., via a generic trainingdata) as well as implicitly trained (e.g., via observing user behavior,user interaction with components, user preferences, historicalinformation, receiving extrinsic information). For example, supportvector machines may be configured via learning or training phase withina classifier constructor and feature selection module. Thus, theclassifier(s) may be used to automatically learn and perform a number offunctions, including but not limited to determining, according tohistorical data, suggestions for gain and/or sensitivity settings. Thislearning may be on an individual basis, i.e., based solely on a singleuser, or may apply across a set of or the entirety of the user base.Information from the users may be aggregated and the classifier(s) maybe used to automatically learn and perform a number of functions basedon this aggregated information. The information may be dynamicallydistributed, such as through an automatic update, a notification, or anyother method or means, to the entire user base, a subset thereof or toan individual user.

These high level-processing techniques may be used to analyze andleverage data within the system. Additionally, they exemplify howinternet/third party connectivity and web-based data can be leveraged.Additionally or alternatively, these techniques may be logged, archived,and applied on an individualized basis (e.g., an ID for a particularcomponent or system, a user profile, etc.). Finally, high levelprocessing techniques can further inform or guide the crosscheckingprocesses described herein.

As with other components, the master control can draw power from thevehicle or be provided with its own primary, renewable, or rechargeablepower supply. For the sake of clarity, as used herein, references to thebrake controller will typically be synonymous with the master controland vice versa, depending upon the context of the disclosure, althoughit will be understood that alternative embodiments using any of thealternative master controls are also contemplated. Also, in someembodiments, the master control may encompass the communications andinformation storage devices, to provide more defined functionality andassist in potential troubleshooting of system and/or componentperformance.

Access to the various forms of data (e.g., sensed, user input, andweb-based), combined with the communications, information storage, andprocessing functionality of the system (either by way of a dedicatedmaster control or a distributed/networked embodiment thereof), allowsfor further analysis of the data and system, as well as how each isused, both on a micro- and macro-scale. For example, this data may helpto verify whether scheduled maintenance, software and system updates,and/or any warranties for components are applicable. The data (includinginformation about system usage) may also be aggregated from amultiplicity of end users to inform future designs and updates, as wellas track and improve safety performance. To the extent the end usersoperate the system under individualized user profiles (and in additionto any unique identifiers assigned to the master control for handlingweb-based data and other inputs/outputs), this aggregation of data canbe similarly individualized, aggregated, and leveraged. For example,biometric data might serve as a theft deterrent or parental control bydisabling or even disengaging components if an unauthorized use oruser/driver is detected.

The aggregated may also provide data that assists in designing futurecomponents. For example, a designer may use aggregated data to learnthat a limited amount of stress is applied to a portion of a component,which may allow the designer to redesign the component to move materialfrom the lower stress area to a higher stress area or remove thematerial entirely.

The resulting system creates a series of interconnected components forthe external vehicle accessories that afford the driver/user withadditional information from and control of these components/addedsystems. By communicating seamlessly and directly with one another (oreven indirectly, to the extent the system incorporates web-based data,external servers, and/or user devices such as mobile phones, tablets,and the like), these external components provide “active control”without driver/user intervention or, as an alternative, by takingcertain actions in the event the driver/user does not respond after aset period.

Examples of specific embodiments and uses for this system will beprovided in greater detail below. Example 1 describes a specific set upfor a trailer brake controller-based system. The series of embodimentsdescribed in Example 2 illustrate how components might interact invarious iterations of the system. Example 3 shows, at a high level, howany given component might interact with its sensors, as well as selectedfunctional aspects of the larger system.

It will be understood that any sensors described above may be applied tothe components below and, to the extent the description below includes aspecific example of a sensor or function, it will be understood thatequivalent sensors and means to accomplish that function arecontemplated. In the same manner, while the description below providesspecific examples of how components may be optimally configured, thefunctional aspects of the larger system may be incorporated intospecific components through the use of sensors and other apparatus asdescribed herein.

Electronics Systems

Brake controllers are envisioned as one of the components in the presentsystem. Generally speaking, a brake controller is an electroniccomponent that allows for activation and releases the brakes in a towedvehicle or trailer. Brake controller actions may be based upon brakingactions, sensed conditions from the towing vehicle, and/or userintervention/inputs for operation. Exemplary, non-limiting brakecontroller units are disclosed in U.S. Pat. Nos. 6,012,780; 6,068,352;6,282,480; 6,445,993; 6,615,125; 8,746,812; 8,789,896; and 9,150,201.All of these patents are incorporated by reference herein.

Within the electronics system, the brake controller may utilize asinputs from the other components any of the following:

-   -   1) ABS: vehicle or trailer ABS system signals may serve as        inputs to modify braking, with the signal originating from a        wheel speed sensor (on the trailer), a brake pedal sensor,        onboard diagnostics, radar, and/or global positioning systems        (GPS);    -   2) Active/inactive: if ignition is active (via on board        diagnostics and/or controller area network bus), then decide the        braking level;    -   3) Actuate: weight distribution, jacks, wheel sensors moved on        incline, or breakaway pin may all serve as action events to        apply the brakes and warn the driver/end user;    -   4) Air Ride: pin box activate the trailer brakes until the air        ride is repaired;    -   5) Angle: the relative angle between the vehicle and trailer can        be used to modify deceleration calculations;    -   6) Auto dimming: on board diagnostics, controller area network        bus, other external components (e.g., interface and ancillary        systems including the communications device), or ambient light        sensors (such as photo cells or photoresistors) may be used for        dimming or other adjustment of the backlights or display;    -   7) Biometrics: the identity of the driver/end user may be stored        for archival purposes and may be used for safety insurance        record access;    -   8) Boost: provided from the communications device and/or        information storage device, or possibly from the brake        controller's settings/operation, and used for output        calculations and/or default value(s);    -   9) Brake intent: originates from a master cylinder pressure or        pressure/movement sensor on the pedal of the vehicle itself and        may be used to calculate the trailer brake controller output;    -   10) Brake output: originates from the trailer brakes and/or        brake control unit and may be used to recalculate braking        parameters based on the difference between the desired and        actual voltages, as well as based on weather conditions and        trailer/vehicle characteristics (weight, make, model, etc.);    -   11) Collision sensor: originates from the hitch, camera,        communications device, global positioning system (GPS), or radar        and may be used to apply the trailer brakes;    -   12) Connect/disconnect: originates from a converter, breakaway        system, or the connections system and may warn the driver/end        user with additional information like intent to move (via the        ignition, wheel speed, GPS, etc.) and/or request additional        action, like extension of the jack;    -   13) Crash detection: originates from a camera or decelerometer        on any device and applies the trailer brakes upon detection;    -   14) Current Voltage: originates from the battery voltage and/or        current from other components and may be used to detect low        battery conditions and/or excessive current;    -   15) Deceleration/acceleration: originates from GPS or wheel        speed and generally correlates to the accelerometer(s), with a        verification and warning if an inconsistency is detected and a        warning provided to the communications device and/or brake        controller;    -   16) Default: based on the vehicle and trailer (including but not        limited to information about the respective weights and other        characteristics thereof), default values of gain and boost may        be calculated or provided via communication device in order to        operate the trailer brake controller;    -   17) Effort: may be expressed as a percentage of use from the        battery in order to indicate battery condition, with this or any        component creating a warning if that component is used above its        usage life, and also warning the end user to change batteries or        perform scheduled maintenance;    -   18) Engagement (mechanical): originates from connection systems        and warns the end user with information like intent to move (via        ignition, wheel speed, GPS, etc.) and/or request additional        action, like extension of the jack;    -   19) Electric over hydraulic (EOH)/electric mode: originates from        the trailer information provided by the communications device        and may be used to set up brake controller default settings;    -   20) Faults: examples include connections systems not fully or        properly engaged or jacks extended, with visual, audible, or        other warnings provided to the user;    -   21) Gain: originates from the communications or information        storage devices and used for trailer brake controller output        calculations, setting of default values, and/or settings for the        brake controller itself;    -   22) Heat: temperature from the trailer brakes and adjusts the        output level;    -   23) High pin: as indicated by pin box or fifth wheel;    -   24) Image: originates from a camera and may be used to look at        alignment of the hitch ball and receiver;    -   25) Lamp type: ZCI indicates lamp types used in the vehicle and        causes stoplight drive with diagnostics potentially fine tuned        accordingly;    -   26) Lane change: originates from a camera and may modify braking        of the trailer;    -   27) Load: originates from a communications device, load sensor,        connection systems (e.g., jack, coupler, fifth wheel, gooseneck,        hitch, hitch bar, etc.), and/or accessory systems (e.g., roof        rack, ramp, securing system, etc.) and causes the trailer brake        controller output calculations and indicates gain, boost, an        application of the brakes, and warning for the end user;    -   28) Location: for purposes of determining weather conditions via        forecast (e.g., high temperatures, rain, wind, etc.) provided by        the communications device, with the brake controller adjusting        to anticipate higher temperatures than may exist in the ambient        conditions and/or adjust gain and boost to anticipate rain;    -   29) Noise: indicative of rough road, wearing of a device and/or        a loose mechanical connection, possibly as measured by a        microphone (for audible) and/or an analog to digital converter        (ADC) camera (for electrical), with the accelerometer inputs        interpreted accordingly and warning indications provided to the        user with respect to premature wear;    -   30) Power loss: may originate and be detected by any component        (e.g., the converter) and be of a short or long term nature,        with a warning provided to the end user;    -   31) Pressure: originates from the TPMS of the trailer and/or if        the fifth wheel airbag pressure is low, with a warning provided        to the user and potential locking of the brakes by the        controller and/or activation of a compressor to provide        appropriate inflation-:    -   32) PWM/multiplex: originates from the towing vehicle and may be        input to the converter, senses brake on/off (BOO) input as PWM;    -   33) Second lock/latch: originates from the connections system        and warns the user accordingly;    -   34) Status: status of the ignition variable from OBD ready to        tow variable from the connection system or camera, with locking        or unlocking the trailer brakes;    -   35) Vertical deceleration: originates from the hitch sensor,        jack, TPMS, weight distribution system, or sway controller        (and/or other components using accelerometers) and establishes        the presence of a bumpy or rough road;    -   36) Warning: may be a warning received from any device which is        then displayed in a coordinated and/or standardized format via        the brake controller display/interface with application of the        brakes as applicable;    -   37) Wear: wear status of the fifth wheel jaw, coupler, and/or        trailer brakes and display warning; and    -   38) Wheel speed: originates from the sway controller, OBD-II        (onboard diagnostics II), GPS, or radar, and brake output may be        reduced at lower speed as the brakes tend to be more efficient        at these speeds, also may permit the selective application of        brakes to only selected wheels and/or in predetermined        sequences.

The brake controller may provide any of the following outputs:

-   -   1) Active/inactive: brake control is active when BOO is active        or manual lever is active;    -   2) Angle: relying on an accelerometer or other similar devices,        the angle of the vehicle and trailer is sensed;    -   3) Auto dimming: ambient light as detected by an appropriate        sensor, such as a photo cell or photoresistor, or by the        controller area network bus;    -   4) Biometrics: may verify the identity of the driver/user based        upon the cameras or other user-provided or user-based        information;    -   5) Boost: as set in the brake controller itself;    -   6) Brake intent: output of brake control is proportional to the        brake intent, which may be measured as noted herein (e., pedal        force and movement detected by an appropriate sensor, pressure        in the brake fluid pressure, etc.);    -   7) Brake output: output as generated by software in the brake        controller itself;    -   8) Charging status: indicative of battery charge in a handheld        unit, as sensed by measuring the charging current;    -   9) Collision sensor: collision detected and deceleration exceeds        a predetermined (or preset) threshold;    -   10) Connect/disconnect: based upon resistive and/or inductive        sensing, the brake controller generates output indicative of        and/or in response to this condition;    -   11) Crash detection: may be detected and communicated based on        the output of an accelerometer exceeding a threshold value        within a specified time;    -   12) Current voltage: the output current is sensed to detect        overload or short to ground, trailer connection etc., and the        battery voltage, referred to hereafter as V_(bat)) adjusts the        average output voltage to keep it constant for the same input        conditions;    -   13) Deceleration/acceleration; indicative signals (as detected,        for example, by an accelerometer, gyroscope, etc.) can be        communicated to other devices and crosschecked or used by the        other device;    -   14) Default: on power up, some settings not adjusted and stored        in memory will be equated to pre-programmed default values if        they are not adjusted/stored in the memory and communicated to        other components;    -   15) Effort: the period of time (e.g., as measured in minutes or        hours) the controller is used may be monitored via software;    -   16) EOH/electric mode: detects the mode in the software using a        connectivity test and may communicated to other components;    -   17) Faults: if conditions (e.g., short to ground, overload,        short to V_(bat), over temperature, battery reversal/improper        connection, etc.) are sensed and the brake controller displays        and/or takes action for continued safe operation;    -   18) Gain: as set in the brake controller itself;    -   19) Heat: as sensed using a thermistor or other similar        apparatus;    -   20) Lamp type: the stoplight drive current sense can depend upon        the type of lamp load (e.g., light emitting diode, incandescent,        etc.);    -   21) Level: sensed in idle condition as well as periodically        during operation (but not while the brakes are activated) using        an accelerometer or like;    -   22) Load: as sensed using current sense during the inductive        test in an idle state;    -   23) Location: as sensed by GPS;    -   24) Noise: preferably detected as audible noises, as may be        generated by road surfaces and especially rough, bumpy, or        irregular surfaces and/or deceleration signal frequency (thereby        suggesting difficult, inconsistent, or otherwise obstructed road        surfaces/conditions);    -   25) Operational frequency: the number, duration, and possibly        other characteristics of specified braking events in a given        period of time (e.g., one day) are stored in memory and        communicated to the interface/ancillary system for statistical        analysis and/or other purposes;    -   26) Power loss: sensed using V_(bat), with short/temporary power        losses avoiding the complete shutdown of the component, while        major/longer term power loss triggers current component        parameters to be saved in memory and restored upon the return of        power;    -   27) Pressure: detected using a pressure transducer in the brake        master cylinder;    -   28) PWM/multiplex: sensed using software within the controller;    -   29) Status: active or inactive;    -   30) Vertical deceleration: sensed using an accelerometer;    -   31) Warning: upon detecting/sensing faults (e.g., short to        ground, open ground, etc.), warning signals will be provided by        the controller;    -   32) Wear: sensed wear in parts as indicated by changes in        specified parameters will be identified by a self-testing        regimen; and    -   33) Wheel speed: as measured using an appropriate sensor, such        as a hall sensor, accelerometer, gyroscope, etc., or as may be        provided by the controller area network.

In some embodiments, sway control units and modules involve apparatusand methods for distributing the weight of a trailer to a towing vehicleand controlling the sway of that trailer relative to the towing vehicle.They may encompass a wide variety of mechanical swing arms, brackets,shoes, slides, spring bars, and related devices that may be attached toany of the draw bar, the ball (or other) mount, the hitch assembly, andthe vehicle itself. Additionally, sway controllers encompass actuators,processors, electronic controls, and/or methods for selectivelycontrolling the mechanical components in such systems. Non-limitingexamples are disclosed in the following United States Patents, all ofwhich are incorporated by reference herein: U.S. Pat. Nos. 5,868,414;7,029,020; and 8,186,702. Moreover, a sway controller may utilize anelectronic system that may not need the weight distribution system. Suchelectronic sway controllers may provide simultaneous braking when swayis detected to all or a portion of the brakes of the trailer. Thesebraking events may generally prevent the trailer from swaying.

The sway controller according to the invention relies on or otherwisereceives the following inputs from other components in the system orsensors within the controller itself:

-   -   1) ABS: vehicle ABS system signals may serve as inputs to modify        braking of the trailer;    -   2) Active/Inactive: if the ignition is not active, the sway        controller will be in sleep mode;    -   3) Actuate: until the vehicle or towed apparatus (e.g., trailer)        is moving as indicated by wheel speed or other means, the sway        control system can be in sleep mode;    -   4) Angle: the relative angle between the vehicle and trailer        (via the connection devices such as the coupler, fifth wheel or        gooseneck hitch, or the pin box) can be used to verify the angle        used for sway controller calculations (as detected by an        accelerometer, gyroscope, etc.);    -   5) Biometrics: the identity of the driver/end user may be stored        for archival purposes and may be used for safety insurance        record access;    -   6) Boost: provided from the communications device and/or        information storage device and used for output calculations        and/or default value(s);    -   7) Brake Intent: originates from a master cylinder pressure or        pressure/movement sensor on the pedal of the vehicle itself and        may be used to compare it with the actual deceleration forces;    -   8) Brake Output: originates from the trailer brakes and may be        used to recalculate based on the difference between the desired        and actual voltage;    -   9) Deceleration/Acceleration: deceleration from any component(s)        may be indicative of the vehicle moving so as to wake up the        sway controller, communications device, and/or trailer brake        controller;    -   10) Faults: sway detection as provided by camera or angle sensor        from the coupler or other connection device and may apply the        trailer brakes based on sway signal characteristics;    -   11) Gain: originates from the communications or information        storage devices and used for trailer brake controller output        calculations, setting of default values, and/or settings for the        sway controller's internal settings and/or the brake controller        itself;    -   12) Heat: temperature from the trailer brakes and adjusts the        output level;    -   13) Image: originates from a camera and may be used to observe        and/or determine any swing relative between the vehicle and the        trailer;    -   14) Lane Change: originates from a camera and may modify braking        of the trailer;    -   15) Level: indicative of the level of the hitch, coupler, and/or        other connection device and adjusts the weight distribution        system accordingly;    -   16) Load: originates from a communications device, load sensor,        connection systems (e.g., jack, coupler, fifth wheel, gooseneck,        hitch, hitch bar, etc.), and/or accessory systems (e.g., roof        rack, ramp, securing system, etc.) and causes the trailer brake        controller output calculations and indicates gain, boost, an        application of the brakes, and warning for the end user;    -   39) Location: for purposes of determining weather conditions via        forecast (e.g., high temperatures, rain, wind, etc.) provided by        the communications device, with the brake controller adjusting        to anticipate higher temperatures than may exist in the ambient        conditions and/or adjust gain and boost to anticipate rain and        more sway if windy;    -   17) Status: ignition active and sway in sleep mode if ignition        is not active;    -   18) Vertical Deceleration: originates from the hitch sensor,        jack, TPMS, weight distribution system, or sway controller        (and/or other components using accelerometers) and establishes        the presence of a bumpy or rough road then the sway module        outputs may be further processed accordingly;    -   19) Warning: signal from break away, battery (e.g., low        battery), power loss, ABS active (vehicle or towed product)        would prompt the sway control to adjust the output.    -   20) Wear: wear signal from any component (involved in such        mechanical action) and send warning to communications device and        the master control;    -   21) Wheel Speed: indicative of trailer movement and originates        from the sway controller, OBD-II (onboard diagnostics II), GPS,        or radar, with the transfer functions of the sway output relying        on speed because the efficiency of the brakes is a function of        speed.

The sway controller may provide any of the following outputs:

-   -   1) Active/Inactive: when lateral swing exceeds a predetermined        threshold, the component will be output to the braking as        active;    -   2) Angle: a camera and/or a transducers at the ball or coupler        may be used to measure angle (as detected by an accelerometer,        gyroscope, etc.);    -   3) Boost: may be a relative value automatically set or selected        based upon characteristics of the towed system/trailer (e.g.,        weight of the trailer, tongue weight, etc.);    -   4) Brake Intent: sensed braking may be detected by a strain        gage, a force gage, or similar sensors positioned within the        vehicle and/or the present system;    -   5) Brake Output: as generated by the sway module itself, and the        outputs may be for each side or each magnet associated with        braking;    -   6) Collision Sensor: collision sensed via decelerometer;    -   7) Connect/Disconnect: based upon resistive and/or inductive        sensing, the brake controller generates output indicative of        and/or in response to this condition    -   8) Crash Detection: rate of change in angle (as detected by an        accelerometer or gyroscope on the sway control, by camera, by        force sensors on the hitch/hitch bar, etc.) may be interpreted        as a crash and a warning signal may be sent to other devices        (and possibly prompt further action, such as entering a “crash        mode”);    -   9) Current Voltage; the output current is sensed to detect        overload, short to ground, or similar conditions and, when such        conditions exist, the drive is disabled, the V_(bat) is sensed,        and/or a notification is provided to the communications device;    -   10) Deceleration/Acceleration: measures deceleration via an        accelerometer;    -   11) Default: upon powering the sway controller module, some        settings will be returned to default values if they are not        adjusted and stored in the memory and communicated to other        components;    -   12) Effort: indicative of the date the module was installed and        its cumulative time of use (and, possibly, more comprehensive        information as to the relative timing of its use and/or other        events);    -   13) Faults: shorted or open brakes, no communication with the        vehicle;    -   14) Gain: may be a relative value automatically set or selected        based upon characteristics of the towed system/trailer (e.g.,        weight of the trailer, tongue weight, etc.);    -   15) Heat: as indicated by an appropriately positioned thermistor        with circuitry provided to sense/calculate a threshold for “over        temperature” conditions;    -   16) Level: as indicated by a tilt sensor;    -   17) Load: sensed using current sense during the inductive test        in the idle state;    -   18) Location: may be sensed by a GPS sensor;    -   19) Noise: preferably detected as audible noises, as may be        generated by road surfaces and especially rough, bumpy, or        irregular surfaces and/or deceleration signal frequency (thereby        suggesting difficult, inconsistent, or otherwise obstructed road        surfaces/conditions);    -   20) Operational Frequency: indicative of hours used based upon        changes in the angle;    -   21) Power Loss: sensed using V_(bat), with short/temporary power        losses avoiding the complete shutdown of the component, while        major/longer term power loss triggers current component        parameters to be saved in memory and restored upon the return of        power;    -   22) Status: indicative of connectivity;    -   23) Vertical Deceleration: as sensed using an appropriate        accelerometer;    -   24) Warning: warning signals will be provided from other        components (e.g., trailer brake controller) upon detecting        various faults (e.g., short to ground, open ground, etc.);    -   25) Wear: based upon a self testing regimen, the module will        detect and indicate wear in its parts by changes to selected        parameters (such as excessive temperature of thermistor in        comparison to brake current or brake current as compared to        deceleration readings in the direction of travel, with anomalous        readings in either being indicative of wear), with potential        prompts for the end user to take further action, such as        increasing the spring tension of the bar, etc.;    -   26) Wheel Speed: as measured using an appropriate sensor, such        as a hall sensor, or as may be provided by the controller area        network.

Converters are devices that couple to the electrical system of avehicle, and especially wiring that controls the taillights, signallights, and the like. Converters then transmit and/or further processthose electrical signals so as to allow for simultaneous operation ofsimilar devices on a corresponding vehicle accessory, such as a traileror hitch mounted cargo carrier or other device. Non-limiting examples ofsuch converters include United States Patent Publication Nos.2014/0001730 and 2015/0367774 and U.S. Pat. Nos. 8,179,142; 9,102,267;and 9,120,424, all of which are incorporated by reference.

Converters useful to the invention utilize the following inputs fromother components in the system or sensors within the unit itself:

-   -   1) Active/Inactive: if the ignition is active and/or the        connectivity status is not connected, verify and notify the        communications device and the information storage/memory device        to extend the jacks and/or apply the trailer brakes;    -   2) Connect/Disconnect: based upon an indication from the brake        controller and/or other component that the trailer is        disconnected and verifies with lamps and notifies the        communications device and the information storage/memory device;    -   3) Current Voltage: originates from the battery voltage and/or        current from other components (e.g., trailer brakes, battery,        trailer brake controller, jacks, etc.) and may be used to detect        low battery conditions and/or excessive current;    -   4) Default: the trailer/towed product will indicate the number        and type of lights present which may be used for verification        based upon current and notify in the event of a discrepancy;    -   5) Faults: low battery voltage and/or excessive current being        drawn from the battery and may notify the communications device        and the information storage/memory device;    -   6) Heat: temperature indicated by the brake controller, brake        magnets, the battery, or other components and, in their inactive        state, may be indicative of the ambient temperature conditions,        and appropriate notification may be provided to the        communications device and the information storage/memory device;    -   7) Lamp Type: based on information about the trailer/towed        product set up received from the communication device and/or        other components, and verifies and notifies of any        discrepancies;    -   8) Power Loss: this input can come from the TBC or other        devices;    -   9) PWM/Multiplex: information on the vehicle and its setup,        which informs the pulse width modulation/multiplex methods, is        received from the communications device or other components and        verified, with notification of any discrepancies, created and        provided to the communications devices or other components;    -   10) Status: ignition active and connectivity status is not        connected and verify/notify communications device and/or        information storage device, while also potentially extending        jack and applying trailer brakes;    -   11) Warning: a warning received from any of the connection        devices may initiate an alteration (e.g., flashing) in the        trailer lights.

In the same manner, converters typically may provide any of thefollowing outputs:

-   -   1) Connect/Disconnect: trailer/towed product connection (or lack        thereof) may be detected via creation of output voltage and a        corresponding detection of current;    -   2) Current Voltage: current is sensed via current and voltage is        sensed via an analog to digital conversion of V_(bat);    -   3) Default: upon powering the converter module, some settings        will be returned to default values if they are not adjusted and        stored in the memory and communicated to other components;    -   4) Effort: the number of braking events, signals (e.g., turn        signal activations, tail light operations, etc.), and similar        items attempted or accomplished within a given time period        (e.g., days, hours, etc.) can be tracked via software and        communicated to the communications device and/or the        interface/ancillary systems, including the cloud, in order to        gather statistical information;    -   5) Faults: software and/or circuitry may be used to sense and        take action in response to certain fault conditions (e.g., short        to ground, V_(bat), over temperature, battery reversal or        improper connection, etc.);    -   6) Heat: as sensed via a thermistor or similar apparatus;    -   7) Lamp Type: as determined using current sense;    -   8) Load: as measured using current sense;    -   9) Location: as sensed via GPS;    -   10) Operational Frequency: by counting the number of times        different inputs are turned on or otherwise activated or        engaged;    -   11) Power Loss: sensed using V_(bat), with short/temporary power        losses avoiding the complete shutdown of the component, while        major/longer term power loss triggers current component        parameters to be saved in memory and restored upon the return of        power;    -   12) PWM/Multiplex: sense if inputs are modulated or multiplexed        to that information may be stored in memory and broadcast        through or beyond the system;    -   13) Status: specifically, idle or active and incandescent or        light emitting diode (although other status may also apply);    -   14) Warning: upon detecting various faults via software or        circuitry (e.g., short to ground, open load, etc.), warning        signals may be communicated;    -   15) Wear: based upon a self-testing regimen, the module will        detect and indicate wear in its parts by changes to selected        parameters (such as excessive temperature change at a given        current or abnormal current sense in relation to the        trailer/towed product type may be indicative of potential        issues).

Breakaway systems are devices that sense the unintended disconnection oftowing systems and devices. These systems may use any variety ofelectric or electromechanical couplings positioned on the vehicle and/orthe connections system components to verify the proximity or actualphysical contact of/between the components in question. Some systems mayalso include automatic brake activation on the trailer (or towed device)when a disconnect is detected. For example, this electromechanicalconnection comprises a safety cable that pulls a key out of a switch boxallowing the circuit in the breakaway system to be completed, therebyproviding power to electrical braking systems or, in the event ofhydraulic brakes, an appropriate activation signal. Additionally, somesystems incorporate rechargeable batteries that may be charged by anauxiliary power wire from the vehicle's trailer connection. Mountingsystems are often provided to ensure that the breakaway system islocated proximate to the trailer and vehicle connection assembly (e.g.,hitch ball, hitch box, etc.).

Breakaway systems that might be incorporated with the invention mayutilize the following inputs from other components in the system orsensors within the system itself:

-   -   1) Active/Inactive: if ignition is active and the 5^(th) wheel        hitch, coupler, gooseneck, or other connection device is not        engaged, send voltage to brakes via the breakaway system;    -   2) Actuate: until the vehicle or towed apparatus (e.g., trailer)        is moving as indicated by wheel speed or other means, the        breakaway system can be in sleep mode;    -   3) Air Ride: pin box activate the trailer brakes until the air        ride is repaired;    -   4) Collision Sensor: originates from the hitch, camera,        communications device, global positioning system (GPS), or radar        and may be used to extend the jack;    -   5) Connect/Disconnect: originates from a trailer brake        controller, converter, breakaway system, or the connections        system and may extend the jack;    -   6) Crash Detection: originates from a camera or decelerometer on        any device and applies the trailer brakes upon detection;    -   7) Current Voltage: originates from the battery voltage and/or        current from other components (e.g., trailer brakes, battery,        trailer brake controller, jacks, etc.) and may be used to detect        low battery conditions and/or excessive current;    -   8) Deceleration/Acceleration: deceleration from any component(s)        may be indicative of the vehicle moving so as to wake up this        component, communications device, and/or trailer brake        controller;    -   9) Engagement (Mechanical): hitch, coupler, 5^(th) wheel,        gooseneck engagement/disengagement would be useful information        to the break away system.    -   10) Faults: a low battery fault may result in verification that        enough voltage will be available quickly provide maximum braking        and/or request/direct shut down of unnecessary power draw from        other components in the system, and particularly those on the        trailer and/or that have been disconnect;    -   11) Heat: temperature from the trailer brakes and adjusts and        optionally report the output level;    -   12) Image: originates from a camera and may be used to observe        and/or determine any break away relative between the vehicle and        the trailer;    -   13) Load: originates from a communications device, load sensor,        connection systems (e.g., jack, coupler, fifth wheel, gooseneck,        hitch, hitch bar, etc.), and/or accessory systems (e.g.,        roof-rack, ramp, securing system, etc.) and causes an        application of the brakes and warning for the end user;    -   14) Location: for purposes of determining weather conditions via        forecast (e.g., high temperatures, rain, wind, etc.) provided by        the communications device, with maximum signal reduced and gain        and boost adjusted in the event of rain;    -   15) Power Loss: may originate and be detected by any component        (e.g., the converter) and be of a short or long term nature,        with a warning provided to the end user;    -   16) PWM/Multiplex: information on the vehicle and its setup,        which informs the pulse width modulation/multiplex methods, is        received from the communications device or other components and        verified, with notification of any discrepancies, created and        provided to the communications devices or other components;    -   17) Status: if the ignition is active and any connection device        (e.g., 5th wheel, couple, gooseneck, etc.) is not engaged and        send voltage to brakes;    -   18) Warning: may be a warning received from any device with        application of the brakes as applicable;    -   19) Wear: wear signal from any component (involved in such        mechanical action) and send warning to communications device and        the master control;    -   20) Wheel Speed: indicative of wheel movement.

The breakaway system also typically provides any of the followingoutputs:

-   -   1) Active/Inactive: monitor voltage and/or current provided to        the brakes;    -   2) Charging Status: this may be sent to the master control to        aid in its decisions with, as an example, low charge status        warning to the user of an issue with respect to the battery;    -   3) Current Voltage: as current or voltage provided to the brake        magnets;    -   4) Default: two axles;    -   5) Faults: overheating, shorted magnet(s), breakaway switch        failure, or trailer brake disconnection from the breakaway        system;    -   6) Heat: the breakaway module may generate heat if the switch's        contact resistance is high due to oxidation, corrosion, or        similar degradation of its surface;    -   7) Location: may be sensed via GPS;    -   8) Status: indicative of connectivity;    -   9) Warning: shorted magnet(s), breakaway active, or lower than        expected voltage/current;    -   10) Wear: contact resistance indirectly measured via temperature        changes (e.g., heat detection) within a predetermined time        frame;

Tire pressure-monitoring systems (TPMS) periodically or continuouslysense the air pressure in one or more tires. As with the othercomponents of the present system, such TPMS devices are separate fromany integrated, closed systems that may be employed by the vehiclemanufacturer to monitor only the vehicle tires. Such systems employpressure sensors operatively connected to one or more of the inflatabletires of a trailer or towed device, with a corresponding receiver forthe TPMS assisting in the operation of the system. These sensors mayprovide signals to a processor and/or memory unit of the TPMS device,which then communicates with the driver/end user through a graphicalinterface, display, or other warning system. Typically, when one or moresensors register pressure readings outside of the predetermined normalrange, an alert is provided to the user.

TPMS devices may utilize any of the following inputs from othercomponents or sensors within the system itself:

-   -   1) Active/Inactive: Ignition active status and/or ABS active        signal would wake up the TPMS;    -   2) Actuate: until the vehicle or towed apparatus (e.g., trailer)        is moving as indicated by wheel speed or other means, the TPMS        system can be in sleep mode;    -   3) Auto Inflate: if low pressure is detected, inflation of the        tires is initiated until a correct pressure is detected;    -   4) Current Voltage: originates from the battery voltage and/or        current from other components (e.g., trailer brakes, battery,        trailer brake controller, jacks, etc.) and may be used to detect        low battery conditions and/or excessive current;    -   5) Faults: too much trailer weight from the communications        device and communicates to the TPMS receiver, so as to notify        and/or verify against other data within the overall system, with        adjustment to gain/boost in the trailer brake controller,        warnings of sway condition, etc., as further possibilities;    -   6) Heat: temperature from the trailer brakes and notifies the        TPMS receiver;    -   7) Location: for purposes of determining weather conditions via        forecast (e.g., high temperatures, rain, wind, etc.) provided by        the communications device, with pressure readings adjusted        according to barometric pressure;    -   8) Power Loss: may originate and be detected by any component        (e.g., the converter) and be of a short or long term nature,        with a warning provided to the end user;    -   9) Pressure: self-generated indication of low pressure and        results in tire inflation;    -   10) Proximity: proximity of TPMS to the TPMS receiver;    -   11) Status: Ignition active status would wake up the TPMS;    -   12) Warning: ABS active warning could serve as a cross check        with potential adjustment to the gain/boost by the brake        controller, etc.;    -   13) Wheel Speed: indicative of wheel movement.

TPMS devices also provide any of the following outputs:

-   -   1) Active/Inactive: indicated as active when wheel rotation is        detected, with request to send pressure or temperature sensed        data or inputs received when queried;    -   2) Current Voltage: may be indicative of low V_(bat);    -   3) Default: indicative of manufacturer's recommended pressures;    -   4) Engagement (Mechanical): the actual pressure reading will be        indicative of correct position of the TPMS;    -   5) Faults: may be no communication and/or out of range pressure;    -   6) Heat: thermistor or similar apparatus detects the temperature        of pressurized air in the tire;    -   7) Location: may be sensed via GPS;    -   8) Operational Frequency: indicative of component starts and        stops, travel time, and/or total tire usage time;    -   9) Pressure: as measured via a pressure transducer;    -   10) Status: indicative of movement of the object associated with        the TPMS;    -   11) Warning: low battery (as sensed by V_(bat)), tire pressure        out of range (as sensed by the pressure transducer), and or high        temperature (as sensed via the thermistor);    -   12) Wear: may be indicated by wheel speed measurements from the        component that are inconsistent with wheel speed inputs provided        from other system components;    -   13) Wheel Speed: as indicated by an accelerometer or other        appropriate device integrated with the TPMS.

Trailer braking units merely activate the brakes on the trailer itself,without necessarily receiving control signals from a separate device(e.g., a trailer brake controller). Brake units may be integrated with atrailer, or a separate after-market kit may be installed on the traileritself. Brake units may be distinguished from brake controller units, inpart, by their location (on the trailer itself) and their need toreceive an additional braking signal—usually provided by the brakecontroller or some other electrical connection with the vehicle itself(e.g., a signal to activate the tail lights, possibly provided by aconverter).

Trailer brakes may utilize any of the following inputs from othercomponents or sensors within the unit itself:

-   -   1) ABS: vehicle ABS system signals may serve as inputs to modify        braking of the trailer;    -   2) Active/Inactive: if ignition is active and the 5^(th) wheel        hitch, coupler, gooseneck, or other connection device is not        engaged, send voltage to brakes;    -   3) Actuate: until the vehicle or towed apparatus (e.g., trailer)        is moving as indicated by wheel speed or other means, the        trailer brake monitor can be in sleep mode;    -   4) Air Ride: pin box activate the trailer brakes until the air        ride is repaired;    -   5) Angle: the relative angle between the vehicle and trailer        (via the connection devices such as the coupler, fifth wheel or        gooseneck hitch, or the pin box) can be used to verify the angle        and apply brakes in response to too much swing amplitude and        frequency;    -   6) Boost: provided from the communications device and/or        information storage device and used to verify settings against        trailer weight, vehicle weight, and the corresponding brake        voltage;    -   7) Brake Intent: provided from the master cylinder pressure or        pressure/movement of a sensor associated with the brake pedal        and used to compare against the corresponding brake voltage;    -   8) Charging Status: of the trailer battery;    -   9) Collision Sensor originates from the hitch, camera,        communications device, global positioning system (GPS), or radar        and may be used to extend the jack;    -   10) Connect/Disconnect originates from a trailer brake        controller, converter, breakaway system, or the connections        system and may extend the jack;    -   11) Crash Detection: originates from a camera or decelerometer        on any device and applies the trailer brakes upon detection;    -   12) Current Voltage: originates from the battery voltage and/or        current from other components (e.g., trailer brakes, battery,        trailer brake controller, jacks, etc.) and may be used to detect        low battery conditions and/or excessive current;    -   13) Deceleration/Acceleration: deceleration from any        component(s) may be indicative of the vehicle moving so as to        wake up this component, communications device, and/or trailer        brake controller;    -   14) Default: the number of axles on the trailer may come from        the communications device based up on the trailer type, but with        a comparison of current vs. voltage verifying the correct number        of axles;    -   15) Faults: tire and/or brake temperature and high V_(BAT)        and/or low V_(BAT) from the battery or the brake controller may        be communicated to the master control for warning purposes;    -   16) Gain: originates from the communications or information        storage devices and used to verify that the voltage of the        brakes (V_(brakes)) do not exceed the gain setting;    -   17) Heat: heating of the trailer brakes;    -   18) Image: originates from a camera and may be used to examine        source of audible noise, as detected/transmitted by a microphone        associated with the camera, from the brakes;    -   19) Lane Change: trailer brake controller informs the brake unit        of a lane change and may instruct to apply brakes directly;    -   20) Load: originates from a communications device, load sensor,        connection systems (e.g., jack, coupler, fifth wheel, gooseneck,        hitch, hitch bar, etc.), and/or accessory systems (e.g., roof        rack, ramp, securing system, etc.) and causes an application of        the brakes and warning for the end user;    -   21) Noise: indicative of rough road, wearing of a device and/or        a loose mechanical connection, with the accelerometer inputs        interpreted accordingly and warning indications provided to the        user with respect to premature wear;    -   22) Power Loss: may originate and be detected by any component        (e.g., the converter) and be of a short or long term nature,        with a warning provided to the end user;    -   23) Pressure: as indicated by TPMS with the brakes applied to        immobilize the trailer;    -   24) Second lock/latch: originates from the connections system        and the jack stays extended until the pin is inserted;    -   25) Status: if the ignition is active and any connection device        (e.g., 5^(th) wheel, couple, gooseneck, etc.) is not engaged and        send voltage to brakes;    -   26) Warning: may be a warning received from any device with        application of the brakes as applicable;    -   27) Wear: wear signal from any component (involved in such        mechanical action) and send warning to communications device and        the master control;    -   28) Wheel Speed: indicative of wheel movement.

Trailer brake units may provide any of the following outputs:

-   -   1) Active/Inactive: via the presence of pressure and/or voltage;    -   2) Actuate: position sensor;    -   3) Boost: Measure the effectiveness based on deceleration value,        could adjust the boost value;    -   4) Brake Intent: as measured using hydraulic pressure or voltage        at the electric brakes;    -   5) Brake Output: voltage reading at the brakes;    -   6) Connect/Disconnect: open circuit or low resistance;    -   7) Current Voltage: analog to digital converter and current        sensing transducer;    -   8) Default: EOH or electric setup in software and also includes        the number of axles;    -   9) Effort: expressed as a percentage based on the average        voltage versus the maximum voltage over a given period;    -   10) EOH/Electric Mode: software and/or component-based memory        stores the type of brakes;    -   11) Faults: using current flow, voltage is measured from an        analog to digital converter associated with a thermocouple for        detecting heat, thereby providing indication of low voltage, low        current, and/or shorts;    -   12) Gain: maximum voltage observed at/by the brake over a given        period of time, with trailer brake, voltage, or deceleration        changing boost if it is determined as inadequate;    -   13) Heat: measured by way of a thermocouple;    -   14) Load: number of axles measured by sensing current load cell        for weight at wheel;    -   15) Location: may be sensed via GPS;    -   16) Noise: audible noise as detected via appropriate sensors        and/or via appropriately situated accelerometer(s);    -   17) Operational Frequency: position sensor, noise sensor;    -   18) Pressure: as measured via a pressure transducer;    -   19) Status: indicative of the presence of voltage and/or        pressure;    -   20) Warning: in the event the thermocouple detects overheating;    -   21) Wear: indicated by total hours used and/or braking for the        same output drive or trailer load less deceleration observed in        a self-testing regimen;    -   22) Wheel Speed: as measured using an appropriate sensor, such        as a hall sensor or a generator.

Camera systems may include one or more cameras mounted on a trailer,cargo carrying system and/or items stowed on such systems, a connectionassembly (as defined herein), and/or on the vehicle itself. Preferably,digital cameras provide immediate, digital data that may be processedand analyzed via appropriate, dedicated circuits, microprocessors,and/or software. In this manner, movement of objects, recognition ofobjects or people, and a number of other known approaches to processingand leveraging image-based data may be employed by the system. Whilecameras normally produce pictures, other optical sensing devices mayalso be encompassed, such as fingerprint sensors, infrared (or othernon-visible light) sensors, and the like.

Cameras may utilize any of the following inputs from other components orsensors within the system itself:

-   -   1) ABS: the camera may be used to examine the vehicle ABS system        and verify operation and status/activity in that regard;    -   2) Active/Inactive: sway active, check lane change status using        camera;    -   3) Angle: the relative angle between the vehicle and trailer        (via the connection devices such as the coupler, fifth wheel or        gooseneck hitch, or the pin box) can be used to verify the angle        communicated to the sway controller;    -   4) Current Voltage: originates from the battery voltage and/or        current from other components (e.g., trailer brakes, battery,        trailer brake controller, jacks, etc.) and may be used to detect        low battery conditions and/or excessive current;    -   5) Deceleration/Acceleration: deceleration from any component(s)        may be indicative of the vehicle moving so as to wake up this        component, communications device, and/or trailer brake        controller;    -   6) Faults: ‘too much sway’ from sway control can be cross        checked by camera;    -   7) High Pin: fifth wheel high pin indicator could be        cross-checked with camera to verify high pin condition;    -   8) Noise: indicative of rough road, wearing of a device and/or a        loose mechanical connection, with the accelerometer inputs        interpreted accordingly and warning indications provided to the        user with respect to premature wear;    -   9) Power Loss: may originate and be detected by any component        (e.g., the converter) and be of a short or long term nature,        with a warning provided to the end user;    -   10) Second lock/latch: originates from the connections system        and the jack stays extended until the pin is inserted;    -   11) Status: sway active and check lane change status using the        camera;    -   12) Warning: shows image (if available) for a warning condition;

Camera systems also may provide any of the following outputs:

-   -   1) Active/Inactive: software can detect camera activity by        pattern change or similar algorithms;    -   2) Angle: detects angle by way of pattern recognition,        integrated angle sensor, or feature extraction;    -   3) Biometrics: may be used for a retina scan or other similar        tests;    -   4) Collision Sensor: collision sensed via decelerometer;    -   5) Connect/Disconnect: as indicated by a lack of communication        from/by the component;    -   6) Current Voltage: measured via V_(bat) and current;    -   7) Default: for both hardware and software, as depending upon        the original equipment manufacturer's determinations for the        particular camera in use;    -   8) Faults: indicative of improper positioning, with software        potentially programmed to manage and track these conditions;    -   9) Heat: sensed by a thermistor and electronics or other,        similar apparatus;    -   10) Image: by way of still photos, video, or other moving        images, whether based on visible, infrared, or ultraviolet        spectra;    -   11) Location: may be sensed via GPS;    -   12) Operational Frequency: indicative of how often the component        has been turned on/activated and/or the number of times it has        received a request from other components;    -   13) Power Loss: as measured according to V_(bat));    -   14) Proximity: in particular, the edge of the trailer/towed        product, the vehicle perimeters (e.g., bumpers, fenders, wheels,        other extremities, etc.), and/or the connection device, as        detected relying on appropriate recognition software;    -   15) Status: as working and/or active;    -   16) Warning: indicative of low battery or a malfunction of the        camera's hardware or software;    -   17) Wear: as indicated by quiescent current.

All of the foregoing inputs and outputs for the components of theelectronics systems are merely exemplary and do not necessarily limitthe ability to provide other inputs and/or outputs described herein.Further, while these systems are described as electronic systems, theconnection devices and accessory devices described below (as well asthose systems otherwise included or described herein) may includeelectronic components and systems.

Connection Devices

Fifth wheel hitches are trailer connection devices as well known in theart. Generally speaking, these components are usually mounted in orunder the bed of a pick-up truck or similar consumer vehicle. A kingpinon the trailer/towed product cooperates with crescent-shaped set of jawsto allow for the connection of the trailer while simultaneouslypermitting a range of motion between the trailer and vehicle. Additionalmechanisms are incorporated to ensure the hitch is securely fastened tothe vehicle, the kingpin is properly seated, and the entire assembly hassufficient range of motion to allow the vehicle and trailer to turn. Themounting is also designed to evenly and appropriately distribute theweight of the towed apparatus. Non-limiting examples of such fifth wheelhitches include United States Patent Publication Nos. 20140265244,20120018979, 20120018978 and U.S. Pat. No. 7,556,278, all of which areincorporated by reference.

The fifth wheel hitch components used in various embodiments of theinvention may utilize as inputs any of the following conditions:

-   -   1) Active/Inactive: if the ignition is active but the fifth        wheel hitch is not engaged, then extend the jack and apply the        trailer brakes;    -   2) Actuate: when vehicle motion is detected (e.g., as evidenced        by wheel speed) and fifth wheel hitch is not engaged, then        extend the jack;    -   3) Angle: the angle between the vehicle and the trailer/towed        product, as evidenced by the coupler, gooseneck and/or pin box,        with verification of the angle sensed communicated to the sway        controller and/or other components;    -   4) Biometrics: identity of the driver/end user can be stored for        record keeping/archival purposes, as well as used for safety        insurance record access, with the possibility of disabling        operation in response thereto;    -   5) Brake Intent: originates from a master cylinder pressure or        pressure/movement sensor on the pedal of the vehicle itself and        may be used to compare against actual/sensed deceleration        forces;    -   6) Connect/Disconnect: originates from a converter, breakaway        system, or the connections system and request additional action,        like extension of the jack;    -   7) Crash Detection: vehicle movement would prevent disengagement        and an automatic connect or disconnect can be based upon vehicle        speed (e.g., moving=locked, not moving=open);    -   8) Current Voltage: originates from the battery voltage and/or        current from other components (e.g., trailer brakes, battery,        trailer brake controller, converter, jack, etc.) and may be used        to detect low battery conditions and/or excessive current;    -   9) Deceleration/Acceleration: indicative of deceleration,        consistent with vehicle movement, as sensed or indicated by any        component, resulting in a verification that the fifth wheel        hitch is engaged and/or a warning to the communication device        and/or master control;    -   10) Default: default trailer weight from communications device        (used to assess force on jaw);    -   11) Engagement (Mechanical): converter and TBC can detect        trailer self-connection (to the vehicle), with self-detection        also possible;    -   12) Faults: ignition on and trailer/towed product movement,        results in extension of jack(s) if the fifth wheel hitch is not        engaged;    -   13) High Pin: origination point for high pin information/sensed        data;    -   14) Image: originates from a camera and may be used to look at        alignment of the fifth wheel hitch;    -   15) Load: indicative of communications device, load sensor,        jack, fifth wheel hitch, gooseneck, hitch/hitch bar, roof rack,        securing systems, and/or ramp, resulting in a signal to the        communications device to apply the brakes and warn the user;    -   16) Noise: indicative of rough road, wearing of a device and/or        a loose mechanical connection, possibly as measured by a        microphone (for audible) and/or an analog to digital converter        (ADC) camera (for electrical), with the accelerometer inputs        interpreted accordingly and warning indications provided to the        user with respect to premature wear;    -   17) Power Loss: may originate and be detected by any component        (e.g., the converter) and be of a short or long term nature,        with a warning provided to the end user;    -   18) Proximity: indicative of proximity of the trailer ball to        the jaws and may result in movement of the vehicle to attain        proper alignment;    -   19) Second lock/latch: self-indication;    -   20) Status: if the is ignition active but the fifth wheel hitch        is not engaged, then extend the jack and apply the trailer        brakes;    -   21) Vertical Deceleration: originates from the hitch sensor,        jack, TPMS, weight distribution system, or sway controller        (and/or other components using accelerometers)    -   22) Warning: can't take any action;    -   23) Wear: in response to a wear signal from any other component        (particularly those involved in mechanical operations), a        warning may be sent to the communications device and/or master        control;    -   24) Wheel Speed: indicative of trailer movement, and may be        further indicated by speed data provided from the sway module,        on board diagnostics II, GPS, or radar, with the jack extended        in the event the fifth wheel is not engaged properly so as to        avoid the trailer falling into the vehicle and/or otherwise        causing an accident.

The fifth wheel hitch components used in various embodiments of theinvention may provide as outputs any of the following conditions:

-   -   1) Active/Inactive: by monitoring current or weight/force;    -   2) Actuate: as indicated by jaw position, a pin indicator,        and/or a leg pin;    -   3) Air Ride: indicative of air pressure;    -   4) Angle: as indicated by a tilt sensor or angle sensor, for        example, to measure head movement;    -   5) Auto Inflate: air pressure;    -   6) Brake Intent: sensed braking can be accomplished by strain        gage, force gage, or other appropriately selected and positioned        sensors;    -   7) Collision Sensor: collision sensed via decelerometer;    -   8) Connect/Disconnect: component can determine by sensing jaw        position and indicator position;    -   9) Crash Detection: a force sensor is incorporated in connection        with force exceeding predetermined thresholds as being        indicative of a crash event;    -   10) Current Voltage: particularly with respect to motorized        units, the output current of the motor is sensed to detect        overload, short to ground, etc., and the V_(bat) is sensed and        drive disabled if over-range is detected, as well as a        notification provided to the communications device;    -   11) Deceleration/Acceleration: measured as deceleration via an        accelerometer;    -   12) Default: ready to hitch based on jaw position capacity        stored in memory of component or as otherwise indicated within        the system;    -   13) Effort: indicative of the date the module was installed and        its cumulative time of use (and, possibly, more comprehensive        information as to the relative timing of its use and/or other        events);    -   14) Engagement (Mechanical): component can determine by sensing        jaw position and indicator position;    -   15) Faults: not engaged and loose fitting, each as sensed by        position and/or proximity sensors;    -   16) High Pin: load sensor or optical sensor;    -   17) Level: as indicated by a tilt sensor;    -   18) Load: as indicated by a camera on the jack, a load sensor        (e.g., a load cell), a tilt sensor, and/or sensed current;    -   19) Location: as indicated by GPS;    -   20) Lube: the communications device may track scheduled        maintenance, date(s) of service, and the like;    -   21) Noise: preferably detected as audible noises, as may be        generated by road surfaces and especially rough, bumpy, or        irregular surfaces and/or deceleration signal frequency (thereby        suggesting difficult, inconsistent, or otherwise obstructed road        surfaces/conditions);    -   22) Operational Frequency: period of time (e.g., hours) the        component was in use as indicated by changes in the angle;    -   23) Power Loss: sensed using V_(bat), with short/temporary power        losses avoiding the complete shutdown of the component, while        major/longer term power loss triggers current component        parameters to be saved in memory and restored upon the return of        power;    -   24) Pressure: detected using a pressure transducer in an air bag        or other similar device;    -   25) Proximity: relative to other components, particularly for        the purpose of coupling, with such action sensed via camera or        appropriate proximity sensor(s) (e.g., infrared, ultrasonic,        GPS, laser, inductive, and/or capacitive in nature);    -   26) Second lock/latch: as indicated by the presence of a pin;    -   27) Status: as engaged and/or connected;    -   28) Vertical Deceleration: as indicated by an appropriately        positioned accelerometer;    -   29) Warning: overload or short circuit by current sense, locked        by sensing travel position, and/or over weight capacity rating        by measuring weight;    -   30) Wear: monitors current, such as a strain gage for monitoring        strain on/in the component;

Gooseneck hitches are connection devices well known in the art. Thesecomponents may be mounted in or under the bed of a pick-up truck orsimilar consumer vehicle. A hitch ball protrudes upward from themounting assembly to allow for the connection of the trailer. Additionalmechanisms are incorporated to ensure the hitch ball is securelyfastened to within its mounting and the assembly has sufficient range ofmotion to allow the vehicle and trailer to turn. Non-limiting examplesof such gooseneck hitches include United States Patent Publication No.20130277944 U.S. Pat. Nos. 8,286,986, 8,783,705, and 8,783,706 all ofwhich are incorporated by reference. Moreover, the gooseneck hitch mayinclude safety chain tie down members, such as those disclosed in U.S.Pat. Nos. 8,215,658 and 8,360,458.

Gooseneck components used in various embodiments of the invention mayutilize as inputs any of the following conditions:

-   -   1) Active/Inactive: if ignition is active and gooseneck is not        engaged, then extend jack and apply trailer brakes;    -   2) Actuate: when vehicle motion is detected (e.g., as evidenced        by wheel speed) and fifth wheel hitch is not engaged, then        extend the jack;    -   3) Angle: the angle between the vehicle and the trailer/towed        product, as evidenced by the coupler, gooseneck and/or pin box,        with verification of the angle sensed communicated to the sway        controller and/or other components;    -   4) Biometrics: identity of the driver/end user can be stored for        record keeping/archival purposes, as well as used for safety        insurance record access, with the possibility of disabling        operation in response thereto;    -   5) Brake Intent: originates from a master cylinder pressure or        pressure/movement sensor on the pedal of the vehicle itself and        may be used to compare against actual/sensed deceleration        forces;    -   6) Connect/Disconnect: originates from a converter, breakaway        system, or the connections system and request additional action,        like extension of the jack;    -   7) Crash Detection: vehicle movement would prevent disengagement        and an automatic connect or disconnect can be based upon vehicle        speed (e.g., moving=locked, not moving=open);    -   8) Current Voltage: originates from the battery voltage and/or        current from other components (e.g., trailer brakes, battery,        trailer brake controller, converter, jack, etc.) and may be used        to detect low battery conditions and/or excessive current;    -   9) Deceleration/Acceleration: indicative of deceleration,        consistent with vehicle movement, as sensed or indicated by any        component, resulting in a verification that the fifth wheel        hitch is engaged and/or a warning to the communication device        and/or master control;    -   10) Default: default trailer weight as indicated by the        communications device (used to assess force on jaw);    -   11) Engagement (Mechanical): vehicle movement would prevent        disengagement and an automatic connect or disconnect can be        based upon vehicle speed (e.g., moving=locked, not moving=open);    -   12) Faults: ignition on and trailer/towed product movement,        results in extension of jack(s) if the fifth wheel hitch is not        engaged;    -   13) Image: originates from a camera and may be used to look at        alignment of the fifth wheel hitch;    -   14) Load: indicative of communications device, load sensor,        jack, coupler, fifth wheel hitch, gooseneck, hitch/hitch bar,        roof-rack, securing systems, and/or ramp, resulting in the trail        brake controller output calculations for gain and boot and a        signal to apply the brakes and warn the user;    -   15) Noise: indicative of rough road, wearing of a device and/or        a loose mechanical connection, possibly as measured by a        microphone (for audible) and/or an analog to digital converter        (ADC) camera (for electrical), with the accelerometer inputs        interpreted accordingly and warning indications provided to the        user with respect to premature wear;    -   16) Power Loss: may originate and be detected by any component        (e.g., the converter) and be of a short or long term nature,        with a warning provided to the end user;    -   17) Proximity: indicative of proximity of the trailer ball to        the jaws and may result in movement of the vehicle to attain        proper alignment;    -   18) Second lock/latch: self-indication;    -   19) Status: if ignition is active and gooseneck is not engaged,        then extend jack and apply trailer brakes;    -   20) Vertical Deceleration: originates from the hitch sensor,        jack, TPMS, weight distribution system, or sway controller        (and/or other components using accelerometers) 21) Warning:        can't take any action;    -   22) Wear: in response to a wear signal from any other component        (particularly those involved in mechanical operations), a        warning may be sent to the communications device and/or master        control;    -   23) Wheel Speed: indicative of trailer movement, and may be        further indicated by speed data provided from the sway module,        on board diagnostics II, GPS, or radar, with the jack extended        in the event the gooseneck is not engaged properly so as to        avoid the trailer falling into the vehicle and/or otherwise        causing an accident.

Gooseneck components used in various embodiments of the invention mayprovide as outputs any of the following conditions:

-   -   1) Active/Inactive: by monitoring current or weight/force;    -   2) Actuate: as indicated by the ball position in an up or down        orientation and/or by the safety chain hooks;    -   3) Air Ride: indicative of air pressure;    -   4) Angle: as indicated by a tilt sensor or angle sensor;    -   5) Auto Inflate: air pressure;    -   6) Brake Intent: sensed braking can be accomplished by strain        gage, force gage, or other appropriately selected and positioned        sensors;    -   7) Collision Sensor: collision sensed via decelerometer;    -   8) Connect/Disconnect: component can determine by sensing jaw        position and indicator position, with the current in the jaw        mechanism motor monitored with increases being indicative of        when the pin is positioned correctly;    -   9) Crash Detection: a force sensor is incorporated in connection        with force exceeding predetermined thresholds as being        indicative of a crash event;    -   10) Current Voltage: the output current is sensed to detect        overload, short to ground, etc., and the V_(bat) is sensed and        drive disabled if over-range is detected, as well as a        notification provided to the communications device;    -   11) Deceleration/Acceleration: measured as deceleration via an        accelerometer;    -   12) Default: ready to hitch position capacity stored in memory        of component or as otherwise indicated within the system;    -   13) Effort: indicative of the date the module was installed and        its cumulative time of use (and, possibly, more comprehensive        information as to the relative timing of its use and/or other        events);    -   14) Engagement (Mechanical): component can determine by sensing        jaw position and indicator position, with the current in the jaw        mechanism motor monitored with increases being indicative of        when the pin is positioned correctly;    -   15) Faults: not engaged and loose fitting, each as sensed by        position and/or proximity sensors;    -   16) Level: as indicated by a tilt sensor;    -   17) Load: as indicated by a camera on the jack, a load sensor        (e.g., a load cell), a tilt sensor, and/or sensed current;    -   18) Location: as indicated by GPS;    -   19) Lube: the communications device may track scheduled        maintenance, date(s) of service, and the like;    -   20) Noise: preferably detected as audible noises, as may be        generated by road surfaces and especially rough, bumpy, or        irregular surfaces and/or deceleration signal frequency (thereby        suggesting difficult, inconsistent, or otherwise obstructed road        surfaces/conditions);    -   21) Operational Frequency: period of time (e.g., hours) the        component was in use as indicated by changes in the angle;    -   22) Power Loss: sensed using V_(bat), with short/temporary power        losses avoiding the complete shutdown of the component, while        major/longer term power loss triggers current component        parameters to be saved in memory and restored upon the return of        power;    -   23) Proximity: relative to other components, particularly for        the purpose of coupling, with such action sensed via camera or        appropriate proximity sensor(s) (e.g., infrared, ultrasonic,        GPS, laser, inductive, and/or capacitive in nature);    -   24) Second lock/latch: as indicated by the presence of a pin;    -   25) Status: as engaged and/or connected;    -   26) Vertical Deceleration: as indicated by an appropriately        positioned accelerometer;    -   27) Warning: overload or short circuit by current sense, locked        by sensing travel position, and/or over weight capacity rating        by measuring weight;    -   28) Wear: monitors current, such as a strain gage for monitoring        strain on/in the component;

Pin boxes fix the kingpin at a certain location and angle inrelationship to connection device such as a fifth wheel hitch. The pinbox usually has a box frame made from flat steel plates to accommodateheavy loads, while one or more air bags, shocks, or othermovement-dampening mechanisms positioned within the box frame to helpminimize jostling and unwanted movement between the connectiondevice/vehicle and the towed apparatus/trailer. Non-limiting examples ofsuch pin boxes include United States Patent Publication No. 20130175786and U.S. Pat. Nos. 7,530,591, 7,997,608, 7,712,761, and 8,100,427 all ofwhich are incorporated by reference.

Pin box components used in various embodiments of the invention mayutilize as inputs any of the following conditions:

-   -   1) Active/Inactive: if ignition is active and pin box is not        engaged, then extend jack and apply trailer brakes;    -   2) Actuate: when vehicle motion is detected (e.g., as evidenced        by wheel speed) and fifth wheel hitch is not engaged, then        extend the jack;    -   3) Air Ride: in response to a signal for air pressure, a        compressor or similar device is instructed to provide more air;    -   4) Angle: the angle between the vehicle and the trailer/towed        product, as evidenced by the coupler, gooseneck and/or pin box,        with verification of the angle sensed communicated to the sway        controller and/or other components;    -   5) Biometrics: identity of the driver/end user can be stored for        record keeping/archival purposes, as well as used for safety        insurance record access, with the possibility of disabling        operation in response thereto;    -   6) Connect/Disconnect: originates from a converter, breakaway        system, or the connections system and request additional action,        like extension of the jack;    -   7) Current Voltage: originates from the battery voltage and/or        current from other components (e.g., trailer brakes, battery,        trailer brake controller, converter, jack, etc.) and may be used        to detect low battery conditions and/or excessive current;    -   8) Deceleration/Acceleration: indicative of deceleration,        consistent with vehicle movement, as sensed or indicated by any        component, resulting in a verification that the fifth wheel        hitch is engaged and/or a warning to the communication device        and/or master control;    -   9) Default: default trailer weight from communications device        (used to assess force on j aw);    -   10) Engagement (Mechanical): converter and TBC can detect        trailer self-connection (to the vehicle), with self-detection        also possible;    -   11) Faults: ignition on and trailer/towed product movement,        results in extension of jack(s) if the fifth wheel hitch is not        engaged;    -   12) High Pin: origination point for high pin information/sensed        data;    -   13) Load: indicative of communications device, load sensor,        jack, coupler, fifth wheel hitch, gooseneck, hitch/hitch bar,        roof-rack, securing systems, and/or ramp, resulting in the trail        brake controller output calculations for gain and boot and a        signal to apply the brakes and warn the user;    -   14) Lube: the communications device may track scheduled        maintenance, date(s) of service, and the like;    -   15) Noise: indicative of rough road, wearing of a device and/or        a loose mechanical connection, possibly as measured by a        microphone (for audible) and/or an analog to digital converter        (ADC) camera (for electrical), with the accelerometer inputs        interpreted accordingly and warning indications provided to the        user with respect to premature wear;    -   16) Power Loss: may originate and be detected by any component        (e.g., the converter) and be of a short or long term nature,        with a warning provided to the end user;    -   17) Proximity: indicative of proximity of the trailer ball to        the jaws and may result in movement of the vehicle to attain        proper alignment;    -   18) Second lock/latch: as indicated by fifth wheel or gooseneck        with the jack remaining extended until the pin is inserted;    -   19) Status: if ignition is active and pin box is not engaged,        then extend jack and apply trailer brakes;    -   20) Warning: can't take any action;    -   21) Wear: in response to a wear signal from any other component        (particularly those involved in mechanical operations), a        warning may be sent to the communications device and/or master        control;    -   22) Wheel Speed: indicative of trailer movement, and may be        further indicated by speed data provided from the sway module,        on board diagnostics II, GPS, or radar, with the jack extended        in the event the gooseneck is not engaged properly so as to        avoid the trailer falling into the vehicle and/or otherwise        causing an accident.

Pin box components used in various embodiments of the invention mayprovide as outputs any of the following conditions:

-   -   1) Active/Inactive: by monitoring current or weight/force;    -   2) Actuate: as indicated by latch mechanism and/or angle of the        pin box relative to the trailer/towed product;    -   3) Air Ride: indicative of air pressure;    -   4) Angle: as indicated by a tilt sensor or angle sensor, for        example, to measure head movement;    -   5) Auto Inflate: air pressure;    -   6) Brake Intent: sensed braking can be accomplished by strain        gage, force gage, or other appropriately selected and positioned        sensors;    -   7) Collision Sensor: collision sensed via decelerometer;    -   8) Connect/Disconnect: component can determine by sensing jaw        position and indicator position, with the current in the jaw        mechanism motor monitored with increases being indicative of        when the pin is positioned correctly;    -   9) Crash Detection: a force sensor is incorporated in connection        with force exceeding predetermined thresholds as being        indicative of a crash event;    -   10) Current Voltage: the output current is sensed to detect        overload, short to ground, etc., and the V_(bat) is sensed and        drive disabled if over-range is detected, as well as a        notification provided to the communications device;    -   11) Deceleration/Acceleration: measured as deceleration via an        accelerometer;    -   12) Default: ready to hitch position;    -   13) Effort: indicative of the date the module was installed and        its cumulative time of use (and, possibly, more comprehensive        information as to the relative timing of its use and/or other        events);    -   14) Engagement (Mechanical): component can determine by sensing        jaw position and indicator position, with the current in the jaw        mechanism motor monitored with increases being indicative of        when the pin is positioned correctly;    -   15) Faults: not engaged and loose fitting, each as sensed by        position and/or proximity sensors;    -   16) Heat: as indicated by thermistor and electronics;    -   17) High Pin: load sensor or optical sensor;    -   18) Level: as indicated by a tilt sensor;    -   19) Load: as indicated by a camera on the jack, a load sensor        (e.g., a load cell), a tilt sensor, and/or sensed current;    -   20) Location: as indicated by GPS;    -   21) Lube: the communications device may track scheduled        maintenance, date(s) of service, and the like;    -   22) Noise: preferably detected as audible noises, as may be        generated by road surfaces and especially rough, bumpy, or        irregular surfaces and/or deceleration signal frequency (thereby        suggesting difficult, inconsistent, or otherwise obstructed road        surfaces/conditions);    -   23) Operational Frequency: period of time (e.g., hours) the        component was in use as indicated by changes in the angle;    -   24) Power Loss: sensed using V_(bat), with short/temporary power        losses avoiding the complete shutdown of the component, while        major/longer term power loss triggers current component        parameters to be saved in memory and restored upon the return of        power;    -   25) Proximity: relative to other components, particularly for        the purpose of coupling, with such action sensed via camera or        appropriate proximity sensor(s) (e.g., infrared, ultrasonic,        GPS, laser, inductive, and/or capacitive in nature);    -   26) Status: as engaged and/or connected;    -   27) Vertical Deceleration: as indicated by an appropriately        positioned accelerometer;    -   28) Warning: overload or short circuit by current sense, locked        by sensing travel position, and/or over weight capacity rating        by measuring weight;    -   29) Wear: monitors current, such as a strain gage for monitoring        strain on/in the component;

The coupler or coupling system is a mechanism that is fixed (e.g.,welded or bolted) onto the end of trailer connection (i.e., the trailertongue), allowing it to be secured over and pivot about a hitch ball.Examples of known couplers include straight channel, foldaway, round oradjustable tongue, flat mount, A-frame, and other similar types. Thecoupler has a latching mechanism to grip and hold the hitch ball,usually by way of a trigger, thumb, wrap-around yoke, pin fastener, orother similar mechanisms. Non-limiting examples of such couplers includeU.S. Pat. Nos. 7,871,098, and 8,083,250 all of which are incorporated byreference.

Coupler components used in various embodiments of the invention mayutilize as inputs any of the following conditions:

-   -   1) Active/Inactive: if ignition is active and coupler is not        engaged, then extend jack and apply trailer brakes;    -   2) Actuate: when vehicle motion is detected (e.g., as evidenced        by wheel speed) and fifth wheel hitch is not engaged, then        extend the jack;    -   3) Biometrics: identity of the driver/end user can be stored for        record keeping/archival purposes, as well as used for safety        insurance record access, with the possibility of disabling        operation in response thereto;    -   4) Connect/Disconnect: originates from a converter, breakaway        system, or the connections system and request additional action,        like extension of the jack;    -   5) Crash Detection: vehicle movement would prevent disengagement        and an automatic connect or disconnect can be based upon vehicle        speed (e.g., moving=locked, not moving=open);    -   6) Current Voltage: originates from the battery voltage and/or        current from other components (e.g., trailer brakes, battery,        trailer brake controller, converter, jack, etc.) and may be used        to detect low battery conditions and/or excessive current;    -   7) Deceleration/Acceleration: indicative of deceleration,        consistent with vehicle movement, as sensed or indicated by any        component, resulting in a verification that the fifth wheel        hitch is engaged and/or a warning to the communication device        and/or master control;    -   8) Default: default trailer weight from communications device        (used to assess force on j aw);    -   9) Engagement (Mechanical): when hitch bar is engaged in the        hitch, a signal is sent to the communications device and/or the        trailer brake controller;    -   10) Faults: ignition on and trailer/towed product movement,        results in extension of jack(s) if the fifth wheel hitch is not        engaged;    -   11) Image: originates from a camera and may be used to look at        alignment of the fifth wheel hitch;    -   12) Level: indicative of the level of the hitch, with a signal        sent to adjust the weight distribution system accordingly;    -   13) Load: indicative of communications device, load sensor,        jack, fifth wheel hitch, gooseneck, hitch/hitch bar, roof rack,        securing systems, and/or ramp, resulting in a signal to the        communications device to apply the brakes and warn the user;    -   14) Lube: the communications device may track scheduled        maintenance, date(s) of service, and the like;    -   15) Noise: indicative of rough road, wearing of a device and/or        a loose mechanical connection, possibly as measured by a        microphone (for audible) and/or an analog to digital converter        (ADC) camera (for electrical), with the accelerometer inputs        interpreted accordingly and warning indications provided to the        user with respect to premature wear;    -   16) Power Loss: may originate and be detected by any component        (e.g., the converter) and be of a short or long term nature,        with a warning provided to the end user;    -   17) Proximity: indicative of proximity of the trailer ball to        the jaws and may result in movement of the vehicle to attain        proper alignment;    -   18) Second lock/latch: as indicated by fifth wheel or gooseneck        with the jack remaining extended until the pin is inserted;    -   19) Status: if ignition is active and coupler is not engaged,        then extend jack and apply trailer brakes;    -   20) Vertical Deceleration: originates from the hitch sensor,        jack, TPMS, weight distribution system, or sway controller        (and/or other components using accelerometers)    -   21) Warning: can't take any action;    -   22) Wear: in response to a wear signal from any other component        (particularly those involved in mechanical operations), a        warning may be sent to the communications device and/or master        control;    -   23) Wheel Speed: indicative of trailer movement, and may be        further indicated by speed data provided from the sway module,        on board diagnostics II, GPS, or radar, with the jack extended        in the event the gooseneck is not engaged properly so as to        avoid the trailer falling into the vehicle and/or otherwise        causing an accident.

Coupler components used in various embodiments of the invention mayprovide as outputs any of the following conditions:

-   -   1) Active/Inactive: by monitoring current or weight/force;    -   2) Actuate: as indicated by engagement lever, angle with respect        to hitch ball, and/or relative force fore and aft (relative to        the vehicle orientation) of the coupler component to measure        braking and acceleration events;    -   3) Angle: as indicated by a tilt sensor or angle sensor, for        example, to measure head movement;    -   4) Brake Intent: sensed braking can be accomplished by strain        gage, force gage, or other appropriately selected and positioned        sensors;    -   5) Collision Sensor: collision sensed via decelerometer;    -   6) Connect/Disconnect: component can determine by sensing jaw        position and indicator position, with the current in the jaw        mechanism motor monitored with increases being indicative of        when the pin is positioned correctly;    -   7) Crash Detection: a force sensor is incorporated in connection        with force exceeding predetermined thresholds as being        indicative of a crash event;    -   8) Current Voltage: the output current is sensed to detect        overload, short to ground, etc., and unexpected current is        compared to setup parameters or other stored or comparative        information, and then the V_(bat) is sensed and drive disabled        if over-range is detected, as well as a notification provided to        the communications device;    -   9) Deceleration/Acceleration: measured as deceleration via an        accelerometer;    -   10) Default: ready to hitch based on lever position with ready        to receive capacity stored in memory of component or as        otherwise indicated within the system;    -   11) Effort: indicative of the date the module was installed and        its cumulative time of use (and, possibly, more comprehensive        information as to the relative timing of its use and/or other        events);    -   12) Engagement (Mechanical): component can determine by sensing        jaw position and indicator position, with the current in the jaw        mechanism motor monitored with increases being indicative of        when the pin is positioned correctly;    -   13) Faults: not engaged and loose fitting, each as sensed by        position and/or proximity sensors;    -   14) Level: as indicated by a tilt sensor;    -   15) Load: as indicated by a camera on the jack, a load sensor        (e.g., a load cell), a tilt sensor, and/or sensed current;    -   16) Location: as indicated by GPS;    -   17) Lube: the communications device may track scheduled        maintenance, date(s) of service, and the like;    -   18) Noise: preferably detected as audible noises, as may be        generated by road surfaces and especially rough, bumpy, or        irregular surfaces and/or deceleration signal frequency (thereby        suggesting difficult, inconsistent, or otherwise obstructed road        surfaces/conditions);    -   19) Operational Frequency: period of time (e.g., hours) the        component was in use as indicated by changes in the angle;    -   20) Power Loss: sensed using V_(bat), with short/temporary power        losses avoiding the complete shutdown of the component, while        major/longer term power loss triggers current component        parameters to be saved in memory and restored upon the return of        power;    -   21) Proximity: relative to other components, particularly for        the purpose of coupling, with such action sensed via camera or        appropriate proximity sensor(s) (e.g., infrared, ultrasonic,        GPS, laser, inductive, and/or capacitive in nature);    -   22) Second lock/latch: as indicated by the presence of a pin;    -   23) Status: as engaged and/or connected;    -   24) Vertical Deceleration: as indicated by an appropriately        positioned accelerometer;    -   25) Warning: overload or short circuit by current sense, locked        by sensing travel position, and/or over weight capacity rating        by measuring weight;    -   26) Wear: monitors current, such as a strain gage for monitoring        strain on/in the component;

Weight distribution systems fits over or onto a connection device andhelps to balance the load more evenly. Such systems are coupled atopposing ends to the vehicle (e.g., via a hitch receiver) and the towedapparatus. They include a head assembly that connects to the vehicle, aswell as a plurality of spring bars extending out from that assembly. Thespring bars are connected to the trailer (e.g., via chains) at theiropposing end, so as to create tension that distributes the tongue weightmore evenly. Non-limiting examples are disclosed in the following UnitedStates Patents, all of which are incorporated by reference herein: U.S.Pat. Nos. 5,868,414; 7,029,020; and 8,186,702.

Weight distribution components used in various embodiments of theinvention may utilize as inputs any of the following conditions:

-   -   1) Active/Inactive: if ignition is not active, the component may        be placed in sleep mode;    -   2) Actuate: until vehicle and/or trailer movement is sensed        (e.g. via wheel speed), component can be placed in sleep mode;    -   3) Angle: indicative of the angle between the vehicle and        trailer as sensed by any of the connection devices, with        verification of the angle and adjustment of the weight        distribution system as appropriate;    -   4) Biometrics: identity of the driver/end user can be stored for        record keeping/archival purposes, as well as used for safety        insurance record access, with the possibility of disabling        operation in response thereto;    -   5) Deceleration/Acceleration: indicative of deceleration,        consistent with vehicle movement, as sensed or indicated by any        component, resulting in a verification that the fifth wheel        hitch is engaged and/or a warning to the communication device        and/or master control;    -   6) Engagement (Mechanical): Converter and TBC can detect trailer        connection to the truck;    -   7) Faults: any faults associated with the trailer brake        controller, jacks, fifth wheel hitch, coupler, hitch device,        battery, camera, and/or brake unit;    -   8) Heat: preferably indicative of only internal heat;    -   9) Lane Change: when detected, verify the appropriate        adjustments to the weight distribution system;    -   10) Level: indicative of the level at the hitch and/or coupler,        with adjustment of the weight distribution system accordingly;    -   11) Load: indicative of communications device, load sensor,        jack, coupler, fifth wheel hitch, gooseneck, hitch/hitch bar,        roof rack, securing systems, and/or ramp, resulting in a signal        to the communications device to apply the brakes and warn the        user;    -   12) Noise: indicative of rough road, wearing of a device and/or        a loose mechanical connection, possibly as measured by a        microphone (for audible) and/or an analog to digital converter        (ADC) camera (for electrical), with the accelerometer inputs        interpreted accordingly and warning indications provided to the        user with respect to premature wear;    -   13) Second lock/latch: as indicated by fifth wheel or gooseneck        with the jack remaining extended until the pin is inserted;    -   14) Status if ignition is not active, the component may be        placed in sleep mode;    -   15) Warning: can't take any action;    -   16) Wear: in response to a wear signal from any other component        (particularly those involved in mechanical operations), a        warning may be sent to the communications device and/or master        control;

Weight distribution components used in various embodiments of theinvention may provide as outputs any of the following conditions:

-   -   1) Active/Inactive: by monitoring current or weight/force;    -   2) Angle/articulation: as indicated by a tilt sensor or angle        sensor;    -   3) Connect/Disconnect: component can determine by resistive        and/or inductive testing;    -   4) Current Voltage: the output current is sensed to detect        overload, short to ground, etc., and the V_(bat) is sensed and        drive disabled if over-range is detected, as well as a        notification provided to the communications device;    -   5) Default: system present;    -   6) Effort: indicative of the date the module was installed and        its cumulative time of use (and, possibly, more comprehensive        information as to the relative timing of its use and/or other        events);    -   7) Engagement (Mechanical): sensed by proximity sensor and        current;    -   8) Faults: not engaged and loose fitting, each as sensed by        position and/or proximity sensors;    -   9) Heat: as indicated by thermistor and electronics;    -   10) Level: as indicated by a tilt sensor;    -   11) Load: as sensed using an appropriately positioned strain        gage, load cell, or deflection sensor;    -   12) Location: as indicated by GPS;    -   13) Noise: preferably detected as audible noises, as may be        generated by road surfaces and especially rough, bumpy, or        irregular surfaces and/or deceleration signal frequency (thereby        suggesting difficult, inconsistent, or otherwise obstructed road        surfaces/conditions);    -   29) Operational Frequency: period of time (e.g., hours) the        component was in use as indicated by motion;    -   30) Power Loss: sensed using V_(bat), with short/temporary power        losses avoiding the complete shutdown of the component, while        major/longer term power loss triggers current component        parameters to be saved in memory and restored upon the return of        power;    -   31) Proximity: relative to other components, particularly for        the purpose of coupling, with such action sensed via camera or        appropriate proximity sensor(s) (e.g., infrared, ultrasonic,        GPS, laser, inductive, and/or capacitive in nature);    -   32) Second lock/latch: position sensor detects actuation to        secure the component;    -   33) Status: as engaged and/or connected;    -   34) Vertical Deceleration: as indicated by an appropriately        positioned accelerometer;    -   35) Warning: too heavy trailer and/or improper weight        distribution;    -   36) Wear: monitors current, such as a strain gage for monitoring        strain on/in the component;    -   37) Wheel Speed: as measured using an appropriate sensor, such        as a hall sensor, or as may be provided by the controller area        network.

Hitches are devices attached to the chassis or frame of a vehicle toallow additional devices to be employed. Hitches usually include acentrally located, hollow, tubular receiver that serves as a connectionpoint for other apparatus, usually via a standard sized hitch pin andclip assembly. The receiver box is integrally attached to additionalstructure (usually comprising at least one transverse beam, with optionmounting brackets attached to or integrally formed on that beam). Thesebeams/brackets are then secured to the vehicle chassis/frame. Hitchesmay be classified according to standard categories based upon the sizeof the receiver box opening, the gross trailer weight, and the tongueweight capacity of the hitch. Hitches, however, may also includecoupling devices, such as depicted in U.S. Pat. No. 9,150,068, which ishereby incorporated by reference.

Hitch components used in various embodiments of the invention mayutilize as inputs any of the following conditions:

-   -   1) Active/Inactive: if ignition is active and ball on hitch bar        is not engaged to the coupler, then the jacks will extend and        the trailer brakes will be applied;    -   2) Actuate: until vehicle and/or trailer movement is sensed        (e.g. via wheel speed), component can be placed in sleep mode;    -   3) Biometrics: identity of the driver/end user can be stored for        record keeping/archival purposes, as well as used for safety        insurance record access, with the possibility of disabling        operation in response thereto;    -   4) Brake Intent: originates from a master cylinder pressure or        pressure/movement sensor on the pedal of the vehicle itself and        may be used to compare against actual/sensed deceleration        forces;    -   5) Connect/Disconnect: originates from a converter, breakaway        system, or the connections system and request additional action,        like extension of the jack;    -   6) Current Voltage: originates from the battery voltage and/or        current from other components (e.g., trailer brakes, battery,        trailer brake controller, converter, jack, etc.) and may be used        to detect low battery conditions and/or excessive current;    -   7) Engagement (Mechanical): self-input and/or originating from a        separate lock-pin lock arrangement;    -   8) Faults: ignition on and trailer/towed product movement,        results in extension of jack(s) if the fifth wheel hitch is not        engaged;    -   9) Heat: preferably indicative of only internal heat;    -   10) Level: indicative of the level at the hitch and/or coupler,        with adjustment of the weight distribution system accordingly;    -   11) Load: indicative of communications device, load sensor,        jack, coupler, fifth wheel hitch, gooseneck, roof rack, securing        systems, and/or ramp, resulting in a signal to the        communications device to apply the brakes and warn the user;    -   12) Noise: indicative of rough road, wearing of a device and/or        a loose mechanical connection, possibly as measured by a        microphone (for audible) and/or an analog to digital converter        (ADC) camera (for electrical), with the accelerometer inputs        interpreted accordingly and warning indications provided to the        user with respect to premature wear;    -   13) Power Loss: may originate and be detected by any component        (e.g., the converter) and be of a short or long term nature,        with a warning provided to the end user;    -   14) Second lock/latch: as indicated by fifth wheel or gooseneck        with the jack remaining extended until the pin is inserted;    -   15) Status: if ignition is active and ball on hitch bar is not        engaged to the coupler, then the jacks will extend and the        trailer brakes will be applied;    -   16) Warning: can't take any action;    -   17) Wear: in response to a wear signal from any other component        (particularly those involved in mechanical operations), a        warning may be sent to the communications device and/or master        control;    -   18) Wheel Speed: indicative of trailer movement, and may be        further indicated by speed data provided from the sway module,        on board diagnostics II, GPS, or radar, with the transfer        function of the brake output will have the speed in the equation        (because the efficiency of the brakes is a function of speed)        and the sensor at the hitch is assumed to be the input for        calculating the brake output.

Hitch components used in various embodiments of the invention mayprovide as outputs any of the following conditions:

-   -   1) Active/Inactive: by monitoring current or weight/force;    -   2) Actuate: oblong hole in the hitch may measure force fore and        aft of the hitch bar connection (relative to vehicle        orientation) to sense braking and acceleration;    -   3) Brake Intent: sensed braking can be accomplished by strain        gage, force gage, or other appropriately selected and positioned        sensors;    -   4) Connect/Disconnect: component can determine hitch bar        insertion into the hitch via a sensor at the back of the hitch        bar and a separate sensor to sense when the pin is inserted;    -   5) Crash Detection: a force sensor is incorporated in connection        with force exceeding predetermined thresholds as being        indicative of a crash event;    -   6) Current Voltage: the output current is sensed to detect        overload, short to ground, etc., and the V_(bat) is sensed and        drive disabled if over-range is detected, as well as a        notification provided to the communications device;    -   7) Deceleration/Acceleration: measured as deceleration via an        accelerometer;    -   8) Default: ready to receive hitch bar based sensed presence of        pin inserted capacity stored in memory of component or as        otherwise indicated within the system;    -   9) Engagement (Mechanical): component can determine hitch bar        insertion into the hitch via a sensor at the back of the hitch        bar and a separate sensor to sense when the pin is inserted;    -   10) Faults: not engaged and loose fitting, each as sensed by        position and/or proximity sensors;    -   11) Level: as indicated by a tilt sensor;    -   12) Load: as indicated by a camera on the jack, a load sensor        (e.g., a load cell), a tilt sensor, a sensed current, and/or an        oblong hole and sensor fore and aft therein;    -   13) Location: as indicated by GPS;    -   14) Noise: preferably detected as audible noises, as may be        generated by road surfaces and especially rough, bumpy, or        irregular surfaces and/or deceleration signal frequency (thereby        suggesting difficult, inconsistent, or otherwise obstructed road        surfaces/conditions);    -   15) Operational Frequency: period of time (e.g., hours) the        component was in use;    -   16) Power Loss: sensed using V_(bat), with short/temporary power        losses avoiding the complete shutdown of the component, while        major/longer term power loss triggers current component        parameters to be saved in memory and restored upon the return of        power;    -   17) Proximity: relative to other components, particularly for        the purpose of coupling, with such action sensed via camera or        appropriate proximity sensor(s) (e.g., infrared, ultrasonic,        GPS, laser, inductive, and/or capacitive in nature);    -   18) Status: as engaged and/or connected;    -   19) Vertical Deceleration: as indicated by an appropriately        positioned accelerometer;    -   20) Warning: locked by sensing travel position;    -   21) Wear: monitors current, such as a strain gage for monitoring        strain on/in the component;    -   22) Wheel Speed: as measured using an appropriate sensor, such        as a hall sensor, or as may be provided by the controller area        network.

Hitches bars, also referred to as draw bars, are connected to the hitchcomponent and allow for additional clearance between the vehicle andtrailer or towed product. In their most basic form, a hitch bar issimply a tubular member sized to fit/connect to a standard sizedreceiver box on one end and having a separate receiver box formed on itsopposing end (this opposing receiver box need not be the same as the onethat is located on the hitch itself). Hitch bars may be straight orcurved, so as to allow for a change in the relative height of theconnection point with the trailer itself.

Hitch bar components used in various embodiments of the invention mayutilize as inputs any of the following conditions:

-   -   1) Active/Inactive: if ignition is active and ball on hitch bar        is not engaged to the coupler, then the jacks will extend and        the trailer brakes will be applied;    -   2) Biometrics: identity of the driver/end user can be stored for        record keeping/archival purposes, as well as used for safety        insurance record access, with the possibility of disabling        operation in response thereto;    -   3) Brake Intent: originates from a master cylinder pressure or        pressure/movement sensor on the pedal of the vehicle itself and        may be used to compare against actual/sensed deceleration        forces;    -   4) Connect/Disconnect: originates from a converter, breakaway        system, or the connections system and request additional action,        like extension of the jack;    -   5) Engagement (Mechanical): presence of pin to hitch and        connectivity of additional components/accessories (e.g., hitch        bar, pintle, tow hooks, tri-ball, etc.);    -   6) Faults: ignition on and trailer/towed product movement,        results in extension of jack(s) if the fifth wheel hitch is not        engaged;    -   7) Heat: preferably indicative of only internal heat;    -   8) Load: indicative of communications device, load sensor, jack,        coupler, fifth wheel hitch, gooseneck, roof-rack, securing        systems, and/or ramp, resulting in a signal to the        communications device to apply the brakes and warn the user;    -   9) Noise: indicative of rough road, wearing of a device and/or a        loose mechanical connection, possibly as measured by a        microphone (for audible) and/or an analog to digital converter        (ADC) camera (for electrical), with the accelerometer inputs        interpreted accordingly and warning indications provided to the        user with respect to premature wear;    -   10) Proximity: indicative of proximity of the trailer ball to        the jaws and may result in movement of the vehicle to attain        proper alignment;    -   11) Second lock/latch: as indicated by fifth wheel or gooseneck        with the jack remaining extended until the pin is inserted;    -   12) Status: if ignition is active and ball on hitch bar is not        engaged to the coupler, then the jacks will extend and the        trailer brakes will be applied;    -   13) Warning: can't take any action;    -   14) Wear: in response to a wear signal from any other component        (particularly those involved in mechanical operations), a        warning may be sent to the communications device and/or master        control;    -   15) Wheel Speed: indicative of trailer movement, and may be        further indicated by speed data provided from the sway module,        on board diagnostics II, GPS, or radar, with the transfer        function of the brake output will have the speed in the equation        (because the efficiency of the brakes is a function of speed)        and the sensor at the hitch is assumed to be the input for        calculating the brake output.

Hitch bar components used in various embodiments of the invention mayprovide as outputs any of the following conditions:

-   -   1) Active/Inactive: by monitoring current or weight/force;    -   2) Actuate: oblong hole in the hitch may measure force fore and        aft of the hitch bar connection (relative to vehicle        orientation) to sense braking and acceleration;    -   3) Angle/articulation: as indicated by a tilt sensor or angle        sensor;    -   4) Brake Intent: sensed braking can be accomplished by strain        gage, force gage, or other appropriately selected and positioned        sensors;    -   5) Collision Sensor: collision sensed via decelerometer;    -   6) Connect/Disconnect: component can determine trailer        connection by sensing the coupler positioning, with the current        in the coupler mechanism motor monitored with increases being        indicative of when the hitch ball is positioned correctly;    -   7) Crash Detection: a force sensor is incorporated in connection        with force exceeding predetermined thresholds as being        indicative of a crash event;    -   8) Current Voltage: the output current is sensed to detect        overload, short to ground, etc., and the V_(bat) is sensed and        drive disabled if over-range is detected, as well as a        notification provided to the communications device;    -   9) Deceleration/Acceleration: measured as deceleration via an        accelerometer;    -   10) Default: ready to hitch position capacity stored in memory        of component or as otherwise indicated within the system;    -   11) Effort: indicative of the date the module was installed and        its cumulative time of use (and, possibly, more comprehensive        information as to the relative timing of its use and/or other        events);    -   12) Engagement (Mechanical): component can determine trailer        connection by sensing the coupler positioning, with the current        in the coupler mechanism motor monitored with increases being        indicative of when the hitch ball is positioned correctly;    -   13) Faults: pin not inserted and too much trailer weight, each        as may be measured by proximity and/or force sensors;    -   14) Heat: as indicated by thermistor and electronics;    -   15) Level: as indicated by a tilt sensor;    -   16) Load: as indicated by a camera on the jack, a load sensor        (e.g., a load cell), a tilt sensor, a sensed current, and/or an        oblong hole and sensor fore and aft therein;    -   17) Location: as indicated by GPS;    -   18) Lube: the communications device may track scheduled        maintenance, date(s) of service, and the like;    -   19) Noise: preferably detected as audible noises, as may be        generated by road surfaces and especially rough, bumpy, or        irregular surfaces and/or deceleration signal frequency (thereby        suggesting difficult, inconsistent, or otherwise obstructed road        surfaces/conditions);    -   23) Operational Frequency: period of time (e.g., hours) the        component was in use;    -   24) Power Loss: sensed using V_(bat), with short/temporary power        losses avoiding the complete shutdown of the component, while        major/longer term power loss triggers current component        parameters to be saved in memory and restored upon the return of        power;    -   25) Proximity: relative to other components, particularly for        the purpose of coupling, with such action sensed via camera or        appropriate proximity sensor(s) (e.g., infrared, ultrasonic,        GPS, laser, inductive, and/or capacitive in nature);    -   26) Second lock/latch: indicative of presence of a pin (e.g., a        cotter pin);    -   27) Status: as engaged and/or connected;    -   28) Vertical Deceleration: as indicated by an appropriately        positioned accelerometer;    -   29) Warning: locked by sensing travel position;    -   30) Wear: monitors current, such as a strain gage for monitoring        strain on/in the component;    -   31) Wheel Speed: as measured using an appropriate sensor, such        as a hall sensor, or as may be provided by the controller area        network.

Accessory Systems

Jacks and jacking systems constitute accessories most commonlyassociated with a trailer or towed product, especially proximate to thetrailer tongue. These products help to stabilize the towed product,generally by extending one or more members to engage an object notassociated with the vehicle and to more fully support the weight of thetrailer. Jack assemblies operate according to a wide variety ofprinciples (e.g., screw type, etc.), and they may be deployed andcontrolled manually or a part of a partially or fully automated system.Non-limiting examples of such systems are disclosed in the followingUnited States Patent Nos., all of which are incorporated by referenceherein: RE43535; U.S. Pat. Nos. 6,874,764; 7,325,786; 7,407,151;8,181,983; 8,348,241; 8,523,148; and 8,910,924. Additional examples,also incorporated herein, may be found in United States PatentPublication Nos. 2014/0246637; 2014/0367626; and 2015/0158464.

Within the various accessory systems of the invention, the jack mayutilize as inputs any of the following conditions:

-   -   1) Active/Inactive: an active ignition input in combination with        a positive connectivity status may result in retraction of the        jack;    -   2) Actuate: when motion is detected in either the vehicle or        trailer (e.g., by way of wheel speed) but there is no electrical        connection, the jack may be extended;    -   3) Air Ride: based upon the pin box, the jack may be forced to        remain extended at least until the air ride is repaired;    -   4) Angle/articulation: based upon weight distribution, the jack        may be extended and/or retracted;    -   5) Auto Dimming: dimming signal from other components and/or the        on-board diagnostics or controller area network bus, so as to        modulate the intensity of the light on the jack itself;    -   6) Auto Inflate: based upon the TPMS, air cushion and trailer        weight, check if trailer weight is too high to cause tire        deflation;    -   7) Biometrics: based on the camera and/or communications device,        the user identity can be confirmed;    -   8) Collision Sensor: in response to connection systems, the        camera, the GPS, and/or radar, the jack may be extended;    -   9) Connect/Disconnect: based on the electronics components        (e.g., trailer brake controller, converter, breakaway system,        etc.) and/or connection devices (e.g., fifth wheel, hitch bar,        coupler, gooseneck, pin box, etc.), the jack may be extended;    -   10) Current Voltage: the battery voltage/current and current        provided from any of the other components (e.g., trailer brake        controller, trailer brakes, converter, battery, etc.) may be        used to detect low battery or excessive current situations;    -   11) Default: originates from communication device after        calculations based on trailer weight and/or other parameters,        with a verification and report to other components regarding any        discrepancies;    -   12) Engagement (mechanical): indicative of engagement of other        connection devices (e.g., pin box, fifth wheel hitch, etc.);    -   13) Faults: shorted magnet or misconnection of the trailer may        extend the jack to prevent potential operation of the vehicle;    -   14) Heat: based on the converter, brake controller, and/or other        components and, being indicative of ambient temperature when        those devices are inactive, higher temperatures (relative to        high ambient temperatures) indicative of use of those components        may be sensed;    -   15) High Pin: based on the converter, breakaway system, and/or        connection devices or based on input from the communications        device or master control, the jack may remain extended;    -   16) Image: based on the camera, connection between the trailer        and vehicle or engagement of spring bars or other components        associated with the trailer may be determined;    -   17) Level: based upon the connection devices and/or sway        controller, one or more jacks may be extended or retracted, with        the use of a plurality of jacks further enabling leveling action        within a geometric plane (e.g., a series of jacks may be        independently deployed at the four corners of the trailer to        allow for coordinated leveling action by the present system);    -   18) Load: based on the communications device, connection        devices, roof rack, securing system, ramp, and/or a load sensor,        an appropriate communication can be provided to the brake        controller and/or control system and/or automatic spring bar        engagement may be initiated;    -   19) Lube: based on the communications device or information        storage/memory device, a predetermined schedule can be arranged;    -   20) Power Loss: based on a temporary or long term power loss        detected by any other component may result in a warning signal        provided to the end user;    -   21) Pressure: based upon the TPMS, air cushion and trailer        weight, check if trailer weight is too high to cause tire        deflation;    -   22) Proximity: proximity to the coupler or other connection        device may be established via a proximity sensor, with the jack        being moved via wheels to align to the correct position for        engagement;    -   23) Second lock/latch: based on any appropriate connection        device, the jack would stay extended until a pin or similar        mechanism/device is positioned appropriately;    -   24) Status: based on ignition variable from on board diagnostics        and/or “ready to tow” and “no connection made” variables from        connection devices or camera, the jack may be extended;    -   25) Warning: an appropriate warning from the connection device        may result in extension of the jack;    -   26) Wear: if any of the connection devices indicate wear, a        warning may be generated by way of the brake controller;    -   27) Wheel Speed: indicative of whether the trailer is moving,        based upon information from the sway module, on board        diagnostics, GPS, and/or radar, with the jacks being retracted.

The jack may provide as outputs any of the following conditions:

-   -   1) Active/Inactive: by monitoring the current or pressure;    -   2) Actuate: indicative of travel position;    -   3) Angle: by way of an angle, tilt, or travel position sensor;    -   4) Connect/Disconnect: sensed by measuring current;    -   5) Current Voltage: faults sensed by measuring current and/or        low or high voltage sensed by measuring voltage;    -   6) Default: retract, extend, or travel positions may be stored        in information storage/memory devices;    -   7) Effort: current or pressure sense;    -   8) Engagement (Mechanical): established by a camera associated        with the jack, a load sensor (e.g., load cell, hydraulic sensor,        tilt sensor, etc.), or current sensing;    -   9) Faults: shorted motor, overload, and/or open load as        determined by sensed current;    -   10) Heat: via a thermistor or thermocouple may monitor the        temperature of the motor;    -   11) Level: via a tilt sensor on the jack;    -   12) Load: established by a camera associated with the jack, a        load sensor (e.g., load cell, hydraulic sensor, tilt sensor,        etc.);    -   13) Location: established by GPS;    -   14) Lube: the communications device tracks scheduled        maintenance, as well as the date and other information with        respect to actual services performed;    -   15) Noise: electrical (i.e., current) or audible;    -   16) Operational Frequency: tracks the number and other        information associated with extension, retraction, or other        operation of the jack;    -   17) Power Loss: reports a temporary loss of power;    -   18) Pressure: hydraulic pressure is determined via an        appropriate pressure sensor;    -   19) Proximity: location and proximity to other devices for the        purpose of coupling may be sensed via a camera or other        proximity sensor/scheme (e.g., infrared, ultrasonic, or        laser-based sensors; GPS; inductive or capacitive methods;        etc.);    -   20) Second lock/latch: foot locked into extension;    -   21) Status: with respect to electric or hydraulic operation;    -   22) Vertical Deceleration: by way of an accelerometer;    -   23) Warning: may include overload or short circuit by current        sense, locked by sensing the normal travel position, and/or over        weight capacity rating by measuring the weight;    -   24) Wear: by monitoring current or pressure.

Cargo carriers may take the form of platforms, cargo baskets, hingedboxes, or cargo racks (e.g., bike, kayak, ski, snowboard, and the like)which attach to the receiver hitch or roof rails of a vehicle. Suchcarriers can accommodate additional luggage and cargo, in addition topotentially serving as a stepping platform to allow easier access to theroof of the vehicle (and/or items attached to it). In all embodiments,the cargo is carried on a generally flat, planar surface. In preferredembodiments, the platform has rectangular or other similar shape withits longest length in the transverse direction (relative to movement ofthe vehicle) to minimize the impact on vehicle profile/length whilemaximizing the cargo area. Rails or an enclosure, preferably providedwith a lockable and/or hinged lid, may define the cargo carrying areaalong its periphery. Additionally or alternatively, straps, fasteners,or other similar apparatus may be integrated in or proximate to theplatform, rails, and/or box to ensure the cargo remains on/in thecarrier. If the carrier is rooftop mounted, mechanisms (e.g., closablejaws, C- or J-shaped hooks, etc.) may be provided along its underside toengage and be secured to roof-mounted rails or other attachment pointson the vehicle. In hitch mount iterations, a tubular member attaches toand extends out from one side of the platform to serve as a connectionpoint with a hitch, hitch bar, or other similar connection devicelocated on the vehicle or towed product itself. Cargo carriers may alsoinclude designs that are specific to a particular purpose, such ascarrying bicycles, in which case modifications to the size, shape, andfunctionality of the platform will be apparent (e.g., rather than havinga flat, planar platform, a bicycle carrier may include a platformcomprising only of wheel mounts or an upright bar with a horizontalattachment members secured to the frame of the bicycle(s)).

The cargo carrier may utilize as inputs any of the following conditions:

-   -   1) Active/Inactive: based on active ignition but component is        not fastened/secured, then the jack will be extended and the        trailer brakes applied;    -   2) Biometrics: the identity of the driver/end user may be stored        for archival purposes and may be used for safety insurance        record access;    -   3) Engagement (Mechanical): indicative of use;    -   4) Faults: rough road indication and/or high speed from trailer        brake controller or other components results in tightening of        straps/fasteners;    -   5) Status: ignition active and component not fastened/secured        results in extension of jack and application of trailer brakes;    -   6) Warning: cannot take any action; may use GPS or biometric        information to lock (e.g., trailer brake controller indicates an        unauthorized user, resulting in locking of the carrier).

The cargo carrier may provide as outputs any of the followingconditions:

-   -   1) Active/Inactive: by monitoring current or weight/force;    -   2) Actuate: motion/movement relative to the location of the        component (e.g., the roof of the vehicle), as indicated by an        accelerometer or vibration sensor;    -   3) Angle: by way of an angle or tilt sensor;    -   4) Collision Sensor: collision as sensed via a decelerometer;    -   5) Connect/Disconnect: indicative of position of latch, strap        and/or other mechanism used to secure the device;    -   6) Current Voltage: at the end of travel of the fastener, with        overload and short circuit sensed by measuring current and low        voltage indicated by measuring the battery voltage;    -   7) Default: system present;    -   8) Effort: indicative of the date the module was installed and        its cumulative time of use (and, possibly, more comprehensive        information as to the relative timing of its use and/or other        events);    -   9) Engagement (Mechanical): position of the latch, strap, and/or        other mechanism used to secure the device will be sensed to        detect engagement;    -   10) Faults: not secured as indicated by a position sensor;    -   11) Level: via a tilt sensor on the jack;    -   12) Load: weight as indicated by a load cell, strain gage,        and/or deflection;    -   13) Location: as indicated by GPS;    -   14) Noise: preferably detected as audible noises, as may be        generated by road surfaces and especially rough, bumpy, or        irregular surfaces and/or deceleration signal frequency (thereby        suggesting difficult, inconsistent, or otherwise obstructed road        surfaces/conditions);    -   15) Operational Frequency: period of time (e.g., hours) the        component was in use;    -   16) Power Loss: based on a temporary or long term power loss        detected by any other component may result in a warning signal        provided to the end user;    -   17) Proximity: location and proximity to other devices for the        purpose of coupling may be sensed via a camera or other        proximity sensor/scheme (e.g., infrared, ultrasonic, or        laser-based sensors; GPS; inductive or capacitive methods;        etc.);    -   18) Second lock/latch: position sensor indicates actuation in        order to secure the device;    -   19) Status: connected;    -   20) Vertical Deceleration: by way of an accelerometer;    -   21) Warning: not engaged properly and/or crash;    -   22) Wear: too much wobble as indicated by a vibration sensor.

Roof rack systems are a series of rails or attachment points affixed tothe top of a vehicle. Generally speaking, these systems usually includea plurality of longitudinal rails in combination with one or moretransverse bars. The transverse bar may be adjustably attached to therails so as to allow the user to adjust the number of bars provided, aswell as the relative distance between the bars (understanding that mostroof rack systems include a plurality of transverse bars). The barsand/or the rails may have a cross-sectional profile that is circular,oval, rectangular, or rounded polygonal in nature. The rails are securedto the vehicle itself, possibly via designated installation points orchannels integrated into the vehicle design by the originalmanufacturer. In some embodiments, the longitudinal bars are held inplace by attachment mechanisms, wherein the attachment mechanism isanchored to the vehicle, thereby allowing for more versatility in thesize/length of the rails. Moreover, the roof rack systems may includemechanism to attach cargo thereto, e.g., bike engagement devices, kayakracks, canoe racks, ski racks, snowboard racks, and the like.

Roof rack systems may utilize as inputs any of the following conditions:

-   -   1) Active/Inactive: based on active ignition but component is        not fastened/secured, then the jack will be extended and the        trailer brakes applied;    -   2) Biometrics: the identity of the driver/end user may be stored        for archival purposes and may be used for safety insurance        record access;    -   3) Engagement (Mechanical); self-indicating (e.g., the carrier        is engaged);    -   4) Faults: rough road indication and/or high speed from trailer        brake controller or other components results in tightening of        straps/fasteners;    -   5) Load: as indicated by the communications device, connection        devices (e.g., coupler, fifth wheel, gooseneck, etc.), or        accessories (e.g., jack, roof rack, securing system, ramp,        etc.), with resulting application of brakes and a warning to the        user;    -   6) Noise: indicative of rough road, wearing of a device and/or a        loose mechanical connection, with the accelerometer inputs        interpreted accordingly and warning indications provided to the        user with respect to premature wear;    -   7) Status: ignition active and component not fastened/secured        results in extension of jack and application of trailer brakes;    -   8) Warning: can't take any action; may use GPS or biometric        information to lock (e.g., trailer brake controller indicates an        unauthorized user, resulting in locking of the carrier);    -   9) Wheel Speed: indicative of vehicle movement.

Roof rack systems may provide as outputs any of the followingconditions:

-   -   1) Active/Inactive: by monitoring current or weight/force;    -   2) Actuate: motion/movement relative to the location of the        component (e.g., the roof of the vehicle), as indicated by an        accelerometer or vibration sensor;    -   3) Collision Sensor: collision as sensed via a decelerometer;    -   4) Connect/Disconnect: indicative of position of latch, strap        and/or other mechanism used to secure the device;    -   5) Crash Detection: as may be incorporated in fastening        locations;    -   6) Current Voltage: at the end of travel of the fastener, with        overload and short circuit sensed by measuring current and low        voltage indicated by measuring the battery voltage;    -   7) Deceleration/Acceleration: deceleration as detected by an        appropriately positioned accelerometer;    -   8) Default: system present;    -   9) Effort: indicative of the date the module was installed and        its cumulative time of use (and, possibly, more comprehensive        information as to the relative timing of its use and/or other        events);    -   10) Engagement (Mechanical): position of the latch, strap,        and/or other mechanism used to secure the device will be sensed        to detect engagement;    -   11) Faults: not secured as indicated by a position sensor;    -   12) Level: via a tilt sensor on the jack;    -   13) Load: weight as indicated by a load cell, strain gage,        and/or deflection;    -   14) Location: as indicated by GPS;    -   15) Noise: preferably detected as audible noises, as may be        generated by road surfaces and especially rough, bumpy, or        irregular surfaces and/or deceleration signal frequency (thereby        suggesting difficult, inconsistent, or otherwise obstructed road        surfaces/conditions);    -   16) Operational Frequency: period of time (e.g., hours) the        component was in use;    -   17) Power Loss: based on a temporary or long term power loss        detected by any other component may result in a warning signal        provided to the end user;    -   18) Proximity: location and proximity to other devices for the        purpose of coupling may be sensed via a camera or other        proximity sensor/scheme (e.g., infrared, ultrasonic, or        laser-based sensors; GPS; inductive or capacitive methods;        etc.);    -   19) Second lock/latch: position sensor indicates actuation in        order to secure the device;    -   20) Status: connected;    -   21) Vertical Deceleration: by way of an accelerometer;    -   22) Warning: not engaged properly and/or crash;    -   23) Wear: too much wobble as indicated by a vibration sensor;    -   24) Wheel Speed: as measured using a wheel speed sensor (e.g.,        hall sensor, etc.) and/or as indicated via the controller area        network.

Securing systems include vehicle and/or trailer mounted systems forattaching and releasing cargo to a vehicle and/or trailer. These systemsusually include straps, fasteners, ties, chains, belts, or other similarmechanisms. They may be attached to roof rack systems, cargo carriers,or possibly even the vehicle and/or trailer itself. The straps/fastenersmay be received by a housing that is attached to the system, carrier, orvehicle. The housing may include mechanism that allow for tightening andretraction of the straps/fasteners. Additionally or alternatively, thesesystems could include complete rails to allow the user to position thestraps/fasteners (and/or the housing with which each is associated) asdesired anywhere along the length of the rail. A clasp or othermechanism receives, secures, and/or binds two straps together and/or aclasp mechanism is provided to one housing, with an adjustable length ofstrap/fastener provided to an opposing housing, so that cargo positionedbetween the two housings can be secured.

Securing systems may utilize as inputs any of the following conditions:

-   -   1) Active/Inactive: based on active ignition but component is        not fastened/secured, then the jack will be extended and the        trailer brakes applied;    -   2) Biometrics: the identity of the driver/end user may be stored        for archival purposes and may be used for safety insurance        record access;    -   3) Deceleration/Acceleration: deceleration from any component        may be indicative of vehicle movement, resulting in a system        wake up from sleep and/or status sent to the communications        device and/or master control;    -   4) Engagement (Mechanical): any item to which the strap is        attached, as potentially indicated by position of latch, strap        or other mechanism to sense/detect engagement;    -   5) Faults: rough road indication and/or high speed from trailer        brake controller or other components results in tightening of        straps/fasteners;    -   6) Heat: only indicative of internal heat;    -   7) Load: as indicated by the communications device, connection        devices (e.g., coupler, fifth wheel, gooseneck, etc.), or        accessories (e.g., jack, roof rack, securing system, ramp,        etc.), with resulting application of brakes and a warning to the        user;    -   8) Status: ignition active/acceleration of vehicle and component        not fastened/secured results in extension of jack and        application of trailer brakes;    -   9) Vertical Deceleration: as indicated from hitch sensor; jack,        TPMS, weight distribution system, sway module, or other        components using an appropriately position accelerometer and        indicates presence of a bumpy road for communication to other        devices to protect the component from experiencing additional        stress;    -   10) Warning: can't take any action; may use GPS or biometric        information to tighten or lock (e.g., trailer brake controller        indicates movement without engagement, resulting in tightening,        or movement by an unauthorized user, resulting in locking of the        carrier);    -   11) Wear: as indicated by a wear signal from any mechanical        device, results in a warning to the communications device and/or        master control;    -   12) Wheel Speed: indicative of vehicle movement.

Securing systems may provide as outputs any of the following conditions:

-   -   1) Active/Inactive: by monitoring current or weight/force;    -   2) Actuate: motion/movement relative to the location of the        component (e.g., the roof of the vehicle), as indicated by an        accelerometer or vibration sensor;    -   3) Connect/Disconnect: indicative of position of latch, strap        and/or other mechanism used to secure the device;    -   4) Current Voltage: at the end of travel of the fastener, with        overload and short circuit sensed by measuring current and low        voltage indicated by measuring the battery voltage;    -   5) Default: system present;    -   6) Effort: indicative of the date the module was installed and        its cumulative time of use (and, possibly, more comprehensive        information as to the relative timing of its use and/or other        events);    -   7) Engagement (Mechanical): position of the latch, strap, and/or        other mechanism used to secure the device will be sensed to        detect engagement;    -   8) Faults: not secured as indicated by a position sensor;    -   9) Heat: as indicated by thermistor and electronics;    -   10) Load: weight as indicated by a load cell, strain gage,        and/or deflection;    -   11) Location: as indicated by GPS;    -   12) Noise: preferably detected as audible noises, as may be        generated by road surfaces and especially rough, bumpy, or        irregular surfaces and/or deceleration signal frequency (thereby        suggesting difficult, inconsistent, or otherwise obstructed road        surfaces/conditions);    -   13) Operational Frequency: period of time (e.g., hours) the        component was in use;    -   14) Power Loss: based on a temporary or long term power loss        detected by any other component may result in a warning signal        provided to the end user;    -   15) Proximity: location and proximity to other devices for the        purpose of coupling may be sensed via a camera or other        proximity sensor/scheme (e.g., infrared, ultrasonic, or        laser-based sensors; GPS; inductive or capacitive methods;        etc.);    -   16) Second lock/latch: position sensor indicates actuation in        order to secure the device;    -   17) Status: connected;    -   18) Warning: not engaged properly and/or crash;    -   19) Wear: too much wobble as indicated by a vibration sensor;    -   20) Wheel Speed: as measured using a wheel speed sensor (e.g.,        hall sensor, etc.) and/or as indicated via the controller area        network.

Winches include any device that may deploy and retract ropes, cables,cords, and other similar objects, as well as adjust tension in the same.Usually, winches are motorized and capable of moving or displacing largeobjects. They comprise a spool that may be operatively associated with adrive assembly that is motorized or hand-operated via a crank. The driveassembly may include gears, solenoids, ratchets, and/or pawls to improvesafety and efficiency. If motorized winches are provided, they may beassociated with the vehicle's power or transmission systems, or separateelectric, hydraulic, pneumatic, or combustion engines may be associatedwith the winch itself.

Winches may utilize as inputs any of the following conditions:

-   -   1) Active/Inactive: if ignition is active, connectivity status        is not connected and the connection device (e.g., coupler,        gooseneck, pin box, etc.) is not engaged, then verify and notify        the communications and/or information storage device and act to        extend the jacks and/or apply the trailer brakes;    -   2) Connect/Disconnect: based on the electronics components        (e.g., trailer brake controller, converter, breakaway system,        etc.) and/or connection devices (e.g., fifth wheel, hitch bar,        coupler, gooseneck, pin box, etc.), the jack may be extended;    -   3) Engagement (Mechanical); position of latch, strap or other        mechanism to secure the device is sensed to detect the        engagement;    -   4) Faults: current measurement to detect open, overload or        shorts;    -   5) Heat: only indicative of internal heat;    -   6) Load: as indicated by the communications device, connection        devices (e.g., coupler, fifth wheel, gooseneck, etc.), or        accessories (e.g., jack, roof rack, securing system, ramp,        etc.), with resulting application of brakes and a warning to the        user;    -   7) Lube: based on the communications device or information        storage/memory device, a predetermined schedule can be arranged;    -   8) Noise: indicative of rough road, wearing of a device and/or a        loose mechanical connection, with the accelerometer inputs        interpreted accordingly and warning indications provided to the        user with respect to premature wear;    -   9) Proximity; proximity of object pulled by the winch to the        truck/trailer using camera    -   10) Status: ignition active and connectivity status not        connected (i.e., coupler, fifth wheel, pin box, or other        connection device not engaged) and results in verification and        notification to communications device and/or storage device with        additional extension of jacks and application of trailer brakes;    -   11) Warning: can't take any action; prevents activation if, for        example, TPMS indicates overload;    -   12) Wheel Speed: indicative of vehicle movement.

Winches may provide as outputs any of the following conditions:

-   -   1) Active/Inactive: by monitoring current or weight/force;    -   2) Actuate: a loose cable as indicated by a position sensor;    -   3) Angle/articulation: indicative of activation and/or the        position of the object being pulled by the winch;    -   4) Collision Sensor: collision as sensed via a decelerometer;    -   5) Connect/Disconnect: loads on this component may be detected        by sensing current after actuation of the component;    -   6) Current Voltage: at the end of travel of the fastener, with        overload and short circuit sensed by measuring current and low        voltage indicated by measuring the battery voltage;    -   7) Default: load value;    -   8) Effort: indicative of the date the module was installed and        its cumulative time of use (and, possibly, more comprehensive        information as to the relative timing of its use and/or other        events);    -   9) Engagement (Mechanical): position of the latch, strap, and/or        other mechanism used to secure the device will be sensed to        detect engagement;    -   10) Faults: overload and/or short circuit via current        measurement;    -   11) Heat: as indicated by thermistor and electronics;    -   12) Load: as indicated by a current sense signal;    -   13) Location: as indicated by GPS;    -   14) Noise: preferably detected as audible noises, as may be        generated by road surfaces and especially rough, bumpy, or        irregular surfaces and/or deceleration signal frequency (thereby        suggesting difficult, inconsistent, or otherwise obstructed road        surfaces/conditions);    -   15) Operational Frequency: number of times the component was in        use;    -   16) Power Loss: based on a temporary or long term power loss        detected by any other component may result in a warning signal        provided to the end user;    -   17) Proximity: location and proximity to other devices for the        purpose of coupling may be sensed via a camera or other        proximity sensor/scheme (e.g., infrared, ultrasonic, or        laser-based sensors; GPS; inductive or capacitive methods;        etc.);    -   18) Second lock/latch: position sensor indicates actuation in        order to secure the device;    -   19) Status: connected;    -   20) Warning: overload and/or short circuit;    -   21) Wear: noise as indicated by a vibration sensor;    -   21) Wheel Speed: as measured using a wheel speed sensor (e.g.,        hall sensor, etc.) and/or as indicated via the controller area        network.

Ramp systems are retractable, flat platforms for loading and unloadingcargo from the bed or carrying bay of a vehicle, such as onto the bed ofa pick-up truck. Ramps usually comprise one or two flattened metalsheets. A hook, latch, or other mechanism is provided at one end of eachsheet to secure the ramp to the vehicle. The exposed top surface of theramp is designed for vehicles, people, and cargo to safely traverse overthe ramp, so that it may include traction surfaces and/or tapered endsto allow for smooth transitions on and off the ramp. The materials forthe ramp should be selected for durability, load-bearing capability,weight, and cost. Some ramp systems may include automated or partiallyautomated deployment and retraction systems, usually including a drivemotor and associated mechanism. A storage/stowage mechanism may beincluded to the extent the ramp system is affixed to/mounted on or underthe vehicle. Ramp systems may also be associated with trailers or othertowed products.

Ramp systems may utilize as inputs any of the following conditions:

-   -   1) Active/Inactive: if the ignition is active and the vehicle is        motion (e.g., via wheel speed or other sensors or inputs), the        ramp is positioned for movement/travel;    -   2) Engagement (Mechanical): as indicated by winch, TPMS, or load        sensor and/or based on position of latch/securing mechanism;    -   3) Faults: indicative of failure of securing strap or overload        condition (with potential indication to deactivate associated        system, such as disengagement of winch to prevent pulling        objects up the ramp);    -   4) Status: ignition active and vehicle movement results in ramp        positioned to move;    -   5) Warning: can't take any action for the reasons noted in the        faults of this section (see above);

Ramp systems may provide as outputs any of the following conditions:

-   -   1) Active/Inactive: presence of voltage or pressure;    -   2) Actuate: rattling of the ramp as sensed with a position        sensor and/or accelerometer;    -   3) Angle/articulation: by way of an angle or tilt sensor;    -   4) Effort: indicative of the date the module was installed and        its cumulative time of use (and, possibly, more comprehensive        information as to the relative timing of its use and/or other        events);    -   5) Engagement (Mechanical): position of the latch, strap, and/or        other mechanism used to secure the device will be sensed to        detect engagement;    -   6) Load: as measured with current sense output and should be        proportional to the load;    -   7) Location: as indicated by GPS;    -   8) Operational Frequency: the number of times the component was        deployed;    -   9) Proximity: location and proximity to other devices for the        purpose of coupling may be sensed via a camera or other        proximity sensor/scheme (e.g., infrared, ultrasonic, or        laser-based sensors; GPS; inductive or capacitive methods;        etc.);    -   10) Second lock/latch: so as to secure the component;    -   11) Status: deployed;    -   12) Warning: not engaged properly and/or crash;    -   13) Wear: noise as indicated by a vibration sensor.

Interface and Ancillary Systems

Batteries comprise any number of known devices for supplying electricalcurrent. Typically, batteries rely on electrochemical reactions toproduce current when a load is applied across the battery's terminals.Within the realm of towing and vehicle accessory devices, standardizedconsumer batteries are used.

Batteries are made up of one or more cells in which theelectricity-producing reactions occur. These cells may be primary(non-rechargeable), although rechargeable systems may be more appealingto users. The voltage and other electrical characteristics of thebattery depend on the number of cells incorporated within the battery(and their precise orientation, e.g. in parallel or in series), as wellas the chemical composition of the materials participating in thereaction. Common primary batteries are characterized by their anode andcathode materials, and they may include zinc-manganese dioxide (i.e.,alkaline), lithium-manganese dioxide, zinc-air, lithium-iron disulfide,and carbon zinc cells. Rechargeable batteries include lithium-ionmaterials (encompassing a wide range of intercalating lithium-basedmaterials), nickel-metal hydride, and lead-acid cells.

Within the various accessory systems of the invention, the batteries mayutilize as inputs any of the following conditions:

-   -   1) Active/Inactive: indicated when ignition is on and/or the        trailer is moving, excessive number of components and/or        excessive demand for current (i.e., exceeding a threshold value)        results in disabling non-prioritize components or otherwise        redirecting and reallocating available current to specific        components;    -   2) Current Voltage: as indicated by charging current and battery        voltage, which may be communicated across the present system,        particularly with respect to low voltage indicated by multiple        components;    -   3) Default: as indicated by any component, for example,        breakaway battery current when active may be based on the number        of axles, with a verification made during periodic self-testing        regimens;    -   4) Faults: total current too high or low as indicated by the        communications device, with the communications device also        reporting current and heat for individual components and the        entire system;    -   5) Heat: indicative of only internal heat for this component;    -   6) Power Loss: as indicated by any component, whether temporary        or of a longer term nature, with a warning provided to the end        user;    -   7) Status: amount of current in use, thereby allowing a        determination on a component-by-component basis as to how to        allocate and/or prioritize remaining capacity;    -   8) Warning: indicative of excessive current with a resulting        decision to disable certain components and/or send requests.

Within the various accessory systems of the invention, the batteries mayprovide as outputs any of the following conditions:

-   -   1) Active/Inactive: indicated as active when load is connected,        with current varying according to the load so that the current        may be monitored and communicated to other components;    -   2) Current Voltage: battery charged or charging;    -   3) Default: output voltage at a nominal 13.5 volts;    -   4) Faults: deep discharge, which may be communicated to other        components;    -   5) Heat: thermistor and electronics;    -   6) Load: battery connected to load and supplying current;    -   7) Location: as indicated by GPS;    -   8) Status: amount of current in use, thereby allowing a        determination on a component-by-component basis as to how to        allocate and/or prioritize remaining capacity, low or high        voltage, too much current drawn;    -   9) Warning: indicative of low charge, short circuit, and/or        failure to charge;    -   10) Wear; performance will deteriorate with age and charge        cycling, so as to provide dead battery detection.

The system also incorporates various communications devices.

Generally speaking, these communications devices may utilize as inputsany input from any component above could also be provided as an input bythe communications device. As non-limiting examples, such inputs couldinclude:

-   -   1) ABS; can come from CAN, OBD II, Wheel speed, TPMS, Radar,        Camera, GPS, Pedal sensor, TBC etc.    -   2) Active/Inactive: IGNITION, TBC, Converter, Jack, Trailer        Brakes, 5^(th) wheel, Gooseneck, Pin Box, Coupler, Sway, Weight        Distribution, Hitches, Cargo Carrier, Roof Rack, Securing        Systems, Winch, Batteries, Breakaway System, TPMS,    -   3) Actuate; Travel position of Jacks, Jaw Position, pin        Indicator of 5^(th) wheel, Ball position of Gooseneck, Latch        mechanism and angle of pin box to trailer in pin Box, Engagement        lever angle with respect to the hitch ball, relative force fore        and aft of coupler to measure braking and acceleration in        coupler, Oblong hole in hitch bar connection, motion relative to        roof in cargo carrier, add all    -   4) Air Ride; Air pressure in 5^(th) wheel, Gooseneck and Pin        Box,    -   5) Angle; Brake Control mounting angle from TBC, Tilt sensor in        jack, 5^(th) wheel, Gooseneck, Pin Box, Coupler, Sway angle from        gyro or accelerometer at ball/coupler or camera behind back of        truck in the center, Tilt sensor in hitch bar, cargo carrier,        Angle sensor in Ramp, Angle Sensor to measure head movement in        5^(th) wheel, Pin Box and coupler    -   6) Auto Dimming: CAN or ambient light sensor in Brake Control,    -   7) Auto Inflate: Air pressure from 5^(th) wheel, Gooseneck or        Pin Box    -   8) Biometrics: Using camera for retina scan or fingerprint        scanning    -   9) Boost; From TBC via user setting or from calculations by        server or TBC or other master controller based on trailer        weight, number of axles, truck type, weather, brake condition.    -   10) Brake Intent: From Brake pedal, Brake fluid pressure or        hitch bar pressure. Also from strain gage, force gage,        displacement sensor at 5^(th) wheel, hitch bar, gooseneck, Pin        box, coupler, sway module etc.    -   11) Brake Output: from TBC, Sway module, Trailer Brakes.    -   12) Charging Status: From Battery or Breakaway system.    -   13) Collision Sensor: Accelerometer in TBC, Hitch Bar, Sway        module or any device or camera.    -   14) Connect/Disconnect: Resistive and Inductive test by TBC,        Sway Control, Trailer Brake module, Breakaway system. Current        measurement for Jack. Jaw and indicator position for 5^(th)        wheel, gooseneck, Pin box. Current sense in jaws movement motor,        sensor in hitches to sense that the pin is inserted, current in        coupler motor, current in winch motor, lack of communication        with camera.    -   15) Crash Detection Accelerometer in TBC, Sway control or any        device, Force or strain gage sensor in 5^(th) wheel, gooseneck,        hitch, hitch bar, coupler, or any device    -   16) Current Voltage: Input of battery voltage and current from        other devices—used to detect low battery condition or excessive        current situation TBC, Battery, Trailer Brakes, Converter, Jack,        Battery etc.    -   17) Deceleration/Acceleration: Deceleration or acceleration from        GPS or wheel speed will correlate to the accelerometer. Input        comes from TBC, Sway control, TPMS or any device with those        sensors. Deceleration or acceleration from any device indicates        that it is moving. This can be used to wake up some devices.    -   18) Default:    -   19) Effort    -   20) Engagement (Mechanical)    -   21) EOH/Electric Mode    -   22) Faults    -   23) Gain: From TBC via user setting or from calculations by        server or TBC or other master controller based on trailer        weight, number of axles, truck type, weather, brake condition    -   24) Heat    -   25) High Pin    -   26) Image    -   27) Lamp Type    -   28) Lane Change    -   29) Level    -   30) Load    -   31) Location    -   32) Lube    -   33) Noise    -   34) Operational Frequency    -   35) Power Loss    -   36) Pressure    -   37) Proximity    -   38) PWM/Multiplex    -   39) Second lock/latch    -   40) Status    -   41) Vertical Deceleration    -   42) Warning: Trailer not connected from TBC, Converter. Low tire        pressure from TPMS, not engaged from 5^(th) wheel, gooseneck,        pin box, coupler, hitch. Crash warning. too much wear warning        from brakes, etc. Excessive current—overload or short from TBC,        Converter, Breakaway, Trailer Brakes. Short to ground from Jack,        winch, TBC, converter, 5^(th) wheel jaw motor, gooseneck, pin        box, weight distribution system or any system with motor or        power drive.    -   43) Wear    -   44) Wheel Speed

Throughout the system, the communications devices may provide as outputsany output from any component above could also be provided as an outputby the communications device. As non-limiting examples, such outputscould include:

-   -   1) Active/Inactive: TBC, jacks, 5^(th) wheel, Gooseneck, Pin        Box, Coupler, Sway, Weight distribution, Hitches, Hitch Bar,        Cargo Carrier, Roof Rack, Security Systems, Converter, Winches,        batteries, breakaway System, TPMS, Trailer Brakes, Cameras,        Ramp—all communicate whether they are active or inactive. For        example, the TBC is active when either brakes are active or        manual lever is pushed. The output of TBC is nonzero in either        case.    -   2) Actuate    -   3) Air Ride    -   4) Angle    -   5) Auto Dimming    -   6) Auto Inflate    -   7) Biometrics    -   8) Boost    -   9) Brake Intent    -   10) Brake Output: The brake output is generated by TBC, Sway        control and is present at the Trailer Brakes. All of them        communicate the details of the output to the communication        device. This will include how much voltage is intended to be        sent to the brakes. The Brakes in turn communicate how much        voltage it received.    -   11) Charging Status    -   12) Collision Sensor    -   13) Connect/Disconnect    -   14) Crash Detection    -   15) Current Voltage    -   16) Deceleration/Acceleration    -   17) Default    -   18) Effort    -   19) Engagement (Mechanical)    -   20) EOH/Electric Mode: The user input will inform the        communication device the type of trailer and number of axles.        The TBC will detect the load and communicate what it found for        load—electric or EOH and including number axles to the        communication device.    -   21) Faults    -   22) Gain    -   23) Heat: Overheated status of devices that have power drive        components and are likely to get hot is communicated to the        communication dev. The thermistor or thermocouple senses the        temperature. The devices like TBC, Jack, 5^(th) wheel,        gooseneck, Sway control, Weight Distribution, Hitch bar,        Securing Systems, Converters, Winches, batteries, Breakaway        system, TPMS, Trailer Brakes, Camera etc. will communicate the        heat status to the communication dev.    -   24) High Pin    -   25) Image    -   26) Lamp Type    -   27) Lane Change    -   28) Level    -   29) Load    -   30) Location    -   31) Lube    -   32) Noise    -   33) Operational Frequency    -   34) Power Loss    -   35) Pressure    -   36) Proximity    -   37) PWM/Multiplex    -   38) Second lock/latch    -   39) Status    -   40) Vertical Deceleration    -   41) Warning    -   42) Wear    -   43) Wheel Speed

Information storage devices are another key aspect of the system. Thesesystems include cloud-based storage, internet or private party servers,hard disk drives, portable storage media (e.g., thumb drives), or anyother, similar electronic storage device. The information storage devicemay also generate information with respect to logging the access orother acquisition of inputs and outputs associated with the device. Anyof the aforementioned inputs and outputs associated with any of theother components in this disclosure may serve as inputs and/or outputs.For the sake of clarity, these will include any combination of thefollowing (as they may be defined/contemplated anywhere in thisdisclosure):

-   -   1) ABS    -   2) Active/Inactive    -   3) Actuate    -   4) Air Ride    -   5) Angle    -   6) Auto Dimming    -   7) Auto Inflate    -   8) Biometrics    -   9) Boost    -   10) Brake Intent    -   11) Brake Output    -   12) Charging Status    -   13) Collision Sensor    -   14) Connect/Disconnect    -   15) Crash Detection    -   16) Current Voltage    -   17) Deceleration/Acceleration    -   18) Default    -   19) Effort    -   20) Engagement (Mechanical)    -   21) EOH/Electric Mode    -   22) Faults    -   23) Gain    -   24) Heat    -   25) High Pin    -   26) Image    -   27) Lamp Type    -   28) Lane Change    -   29) Level    -   30) Load    -   31) Location    -   32) Lube    -   33) Noise    -   34) Operational Frequency    -   35) Power Loss    -   36) Pressure    -   37) Proximity    -   38) PWM/Multiplex    -   39) Second lock/latch    -   40) Status    -   41) Vertical Deceleration    -   42) Warning    -   43) Wear    -   44) Wheel Speed

User Interface Units

Any component, including the master control, may incorporate a userinterface to obtain inputs from the user, to provide information(warnings, status, faults, etc.) to that user, and to generally realizefurther efficiencies for the entire system. These interface items maytake a variety of forms, including but not limited to any combination ofthe following well-known mechanisms:

-   -   1) Liquid crystal display units, cathode ray tubes, light        emitting diodes displays and other video projection devices;    -   2) Touch screens associated with the aforementioned video        devices;    -   3) Dedicated buttons, switches, and/or knobs that may be        indicative of preset conditions or responsive to options        projected by a video device;    -   4) Dedicated status lamps or light emitting diodes;    -   5) Keyboards and numeric keypads;    -   6) Tactile response mechanisms, such as vibration pads or        mechanisms, braille and/or other similar indicating systems; and    -   7) Voice-activated operations, including appropriate        microphones, speakers, and associated processors/software, for        voice-activated commands, synthesized speech, and/or other        audible feedback.

Control System

The master control for the system will be a device that effectivelycoordinates and determines final actions and status for the system.However, the system may not use a master control for a specificcomponent to act. The specific components may communicate amongst oneanother, such as being part of a mesh network, and may act based uponthe information flowing therebetween.

A de facto control system may be inherently established by utilizingstandard software protocols in all or selected components of theelectrical, connection, accessory, and/or interface systems. In thisregard, the end user may not necessarily have a graphic user interfaceor other tangible device representing the control system, but thecoordinated and seamless interaction of the components would effectivelyserve as such a system. In this scenario, further enhancements could berealized by permitting a communications device to effectively act as acontrol panel or dashboard, by way of an application uploaded onto thedevice that enables such actions.

Whatever form the control system takes, the ultimate intent is toprovide the end user with an integrated means of monitoring andinteracting with all of the components in the present system. In thisregard, the control system may display any warning, status, and defaultsetting for each component in the system, and it may further aggregatethese warnings, statuses, and defaults to generate additionalinstructions and recommendations for the user. In some instances, theseinstructions and recommendations could be automatically implemented,particularly to the extent the action relates to safety (e.g., engagingthe brakes and extending the jacks to avoid unintended movement of atrailer, etc.).

Other Components Potentially Associated with the System

Original equipment brakes provided by the vehicle manufacturer mayincorporate specific features, such as anti-lock functionality, thatgenerate additional signals and information that can be useful to thepresent system. These features may be accessed by connecting appropriatecomponents to the on board diagnostics and/or controller area network.

On-board diagnostics systems (OBD) are systems provided by vehiclemanufacturers to identify and share operational information about thevehicle across its various systems. Depending upon the vehiclemanufacturer, it may be possible for end users to easily tie into thissystem in order to monitor, leverage, and reproduce signals andconditions inherent in the OBD for use in the present system.

Controller area network (CAN) bus is the communications line provided bythe vehicle manufacturer. As above, it provides a potential access pointby which end users can potentially tap into existing vehicleinfrastructure.

Example 1

A data collection system and a communication system related to varioustypes of towing systems and assemblies are contemplated. In particular,FIG. 1 illustrates a network system architecture 100 that includes acommunication framework 106 for collecting, processing, andcommunicating data. In combination with interface device 102, thecommunication framework 106 allows data to be sensed at a particulartowing system, including a trailer and/or any number of accessories,and/or assembly device module 110 of the towed and towing vehicles. Aninterface device 102 may be in communication with a computer/processor104 by way of the communication framework 106 such as the internet,network, or cloud as is generally known in the art or as may bedeveloped in the future. The processor 104 and communication framework106 of the system architecture 100 may also include on on-line webserver. The interface device 102 may be a computer, smartphone, tablet,television, laptop, or other device that is accessible by the user toaccess a website application. The towing system device modules 110 maybe in communication with the computer/processor 104 by way of thecommunication framework 106.

The computer/processor 104 of the network system 100 may include adatabase that is configured to receive the sensed data from at least onetowing system device module 110. Sensed data may be collected throughthe communication framework 106 and stored at the database maintainedwithin the computer/processor 104. The collection of sensed data maythen be processed to identify various data sets. The data sets may thenbe communicated to the interface device 102 and/or other aspects of thesystem, such as assembly device module 110.

As illustrated by FIGS. 2 and 3, the device modules 110A-110G associatedwith the particular towing system and accessories, may be located on thetowed vehicle 10 or the towing vehicle 12. The towing systems andaccessories may include, but may not be limited to, a brake controller,a sway module, a jack assembly, a fifth wheel hitch, a gooseneck hitch,a pin box assembly, a coupler, and a weight distribution assembly. Thedevice module representing each of the identified towing systems may bepositioned at various locations of the towed 10 or towing vehicle 12.

The device module 110 may be a sensor or other data gathering deviceassociated with one or more of the towing systems and/or accessories.The device module 110 may include a transceiver configured to transmitand receive information through the communication framework 106, in awired or wireless configuration. Optionally, the network may enablecommunication between at least one internet-accessible website. A“network” can include, but is not limited to, broadband wide-areanetworks such as cellular networks, local-area networks, wirelesslocal-area networks (e.g., Wi-Fi), and personal area networks, such asnear-field or short-distance communication networks includingBLUETOOTH®. Communication across a network may include packet-basedcommunications, radio and frequency/amplitude modulations networks, andany of the other protocols identified herein. Communication may beenabled by hardware elements called “transceivers.” Transceivers may beconfigured for specific networks and a user equipment device may haveany number of transceivers configured for various networks. Forinstance, a smart phone may include a cellular transceiver, a Wi-Fitransceiver, a BLUETOOTH® transceiver, or may be hardwired. In thoseembodiments in which it is hardwired, any appropriate kind or type ofnetworking cables may be utilized. For example, USB cables, mobile phoneadapters, dedicated wires, coaxial cables, optical fiber cables, twistedpair cables, Ethernet, HDMI and the like.

This arrangement, particularly to the extent multiple transceivers areincorporated, gives rise to the possibility of a “mesh network.” Thisnetwork exists among the various devices associated with system 100, andit acknowledges that any number of devices embodying that system maycommunicate seamlessly with one another without the need for specificuser intervention or intervention of a master controller, userinterface, or electronic storage device. The mesh network helps toenable many of the automated features of the disparatedevices/components comprising the system 100.

Examples of such wireless configuration may include, but is not limitedto, various radio access network (RAN), e.g., Wi-Fi, global system formobile communications, universal mobile telecommunications systems,worldwide interoperability for microwave access, enhanced general packetradio service, third generation partnership project long term evolution(3G LTE), fourth generation long term evolution (4G LTE), thirdgeneration partnership project 2, BLUETOOTH®, ultra mobile broadband,high speed packet access, xth generation long term evolution, or anotherIEEE 802.XX technology. Furthermore, embodiments may utilize wiredcommunications.

The interface device 102 may include a user interface 120 as shown inFIG. 1 and elsewhere. The interface device may be in communication withthe communication framework in a wired or wireless configuration. Inembodiments, the interface device 102 may be various access devices,which may include a smart phone, laptop, in-vehicle device, or separateinterface device that retrieves/transmits diagnostic data/information,and other data/information to/from the towing systems via the wired orwireless network. In one embodiment, the interface device 102 may use along-range wireless interface to communicate diagnostic and relatedinformation to the central host computer 104, and to receive relatedinformation from same.

More specifically, in one embodiment, the invention includes a systemfeaturing: 1) a controller; 2) a diagnostic system configured to receivediagnostic information from a host towed or towing vehicle; 3) aposition-locating system configured to determine the towed or towingvehicle location information; 4) a communication interface configured tosend additional information to a peripheral system, and 5) any number oftransceivers configured to receive and/or transmit information throughnetwork such as a wireless transmitter communicating to a wirelessnetwork to an Internet-accessible website.

In certain embodiments, the interface device 102 can include acontroller and a display, such as a touchscreen, an LED or LCD, or anyother type of known or future developed display device. In this case,the controller may feature machine-readable computer code, e.g.,firmware, which controls the display. For example, the computer code canbe configured to render a text message on the display. The text messagecan be sent from the Internet-accessible website, or from a cellulartelephone or the processor 104. The display may be configured to mountinside the vehicle. In various embodiments, the interface device 102 mayinclude a graphics display.

In other embodiments, the interface device 102 may feature a voiceinterface that receives audio information and sends the information tothe wireless transmitter. For example, the access device can be asmartphone that contains a Bluetooth® transceiver configured to sendinformation to and receive information from the network of towingsystems. Alternatively, the access device includes the Bluetooth®transceiver, e.g. it is mounted on an internal circuit board. In stillother embodiments, the interface device includes a short- or long-rangewireless transmitter, e.g. a transceiver operating a Bluetooth®, 802.11,part-15, infrared wireless protocol, or other wired or wirelesscommunication protocol.

The towing system device modules 110A-110G may be a data collectiondevice, a data communication device, or both. The modules may include adata-gathering portion, a data-transmitting portion that transmits theinformation, and a power management portion that supplies power to themodule as needed. The data may be transmitted to a processor 104 thatmay manage communication with each modules and interface device. Theprocessor runs firmware that receives and processes an incoming datamessage, and may acknowledge, interpret, process prospective outputs,and transmit the data through the network. The processor 104additionally receives and processes diagnostic information from modules110. For example, the processor can process diagnostic data as morespecifically identified below.

The processor 104 may store firmware, pre-processed diagnostic data,and/or post-processed diagnostic data in a memory or in a cloud system.The memory may also store a file-managing operating system or databasethat runs on the processor. During operation, the memory canadditionally function as a “data logger” where diagnostic and functionaldata may be captured at high rates (e.g., periodically at intervalsranging anywhere from 1 to 500 milliseconds, with 4 and 200 millisecondsbeing preferred rates) and then read out later.

With firmware, the processor 104 formats information into unique packetsand serially transfers these packets to a wireless modem or the like(such communication protocols may include any known or future developedcommunication protocol, including, without limitation, TCP/IP. Eachformatted packet may include, e.g., a header that describes itsdestination and the wireless modem's numerical identity (e.g., its“phone number”) and a payload that includes the information. Forexample, the packets can include diagnostic or functional datainformation or other information. Once transmitted, the packetspropagate through the network, which delivers them to anInternet-accessible web site.

More specifically, the following features may be performed by varioustowing system and/or accessory device modules 110A-110G. The datacollected may then be communicated through the communication framework106.

As a Data Collection Device:

Fifth wheel hitch/gooseneck coupler and ball 110A: The fifth wheel hitchor gooseneck coupler and ball modules 110A may sense and collect variousdata parameters related to the function of a fifth wheel hitch orgooseneck coupler and ball and/or the conditions under which suchoperates. By way of a non-limiting example, the module 110A may performwarranty or diagnostic type data collection as it relates to cycles,load, trip data, vibration profile, misuses occurred such as loadingwith jaws closed or goose accident, age, trailer weight, a log ofoperational conditions (e.g., sway), and additional sensor information.This information may be utilized for any purpose, such as to determineif a repair is covered by a warranty or was the result of misuse.

Coupler 110B: The coupler module 110B may sense and collect various dataparameters related to the function of a coupler and/or the conditionsunder which such operates. By way of a non-limiting example, the module110B may perform warranty or diagnostic type data collection as itrelates to a coupler safety pin, whether the coupler is connected ordisconnected, load, usage, vibration profile, and misuse or wear.

Jack assemblies 110C: The jack assembly module 110C may sense andcollect various data parameters related to the function of a jackassembly and/or the conditions under which such operates. By way of anon-limiting example, the module 110C may perform warranty or diagnostictype data collection as it relates to load, cycles, position of the jack(extended or retracted), trailer weight, level, travel, pivot, andlubrication, as well as perform automatic user convenience functionssuch as activating a light in dark/night-time conditions.

Sway controller 110D: The sway controller module 110D may sense andcollect various data parameters related to the function of a swaycontroller and/or the conditions under which such operates. By way of anon-limiting example, the module 110D may perform warranty or diagnostictype data collection as it relates to road profile data, wheel speed,number of occurrence of sway control, the magnitude of occurrence ofsway control, trailer conditions, gain, load, pin weight, and number oftimes a warning message is provided to the user.

Brake controller 110E: The brake controller module 110E may sense andcollect various data parameters related to the function of a brakecontroller and/or the conditions under which such operates. By way of anon-limiting example, the module 110E may perform warranty or diagnostictype data collection as it relates to fault codes and occurrences,settings related to gain or boost (including determining whether theyare appropriate for the trailer weight and truck type sensed orindicated to the system), percent output habits of the vehicle operatorincluding time or general usage, trip data, mode usage, age, vibrationprofile, and additional sensor usages.

Pin Box 110F: The pin box module 110F (FIG. 3) may sense and collectvarious data parameters related to the function of a pin box and/or theconditions under which such operates. By way of a non-limiting example,the module 110F may perform warranty or diagnostic type data collectionas it relates to load, cycles, auto inflate or deflate occurrences,connection, disconnect, trip data, and vibration profile.

Weight distribution 110G: The weight distribution module 110G may senseand collect various data parameters related to the function of a weightdistribution assembly and/or the conditions under which such operates.By way of a non-limiting example, the module 110G may perform warrantyor diagnostic type data collection as it relates to cycles, load, usage,pads, profile, number of bar disconnects, clips, and trip data such asturns.

As a Data Communication Device:

Fifth wheel hitch and gooseneck coupler and ball 110A: The fifth wheelhitch and gooseneck coupler and ball module 110A may communicate variousdata parameters related to the function of a fifth wheel hitch orgooseneck coupler and ball and/or the conditions under which suchoperates. By way of a non-limiting example, the module 110A maycommunicate data to identify goose pop up, connection of jaws, andsecond lock latch status. Further, the modules 110A may communicatediagnostic status such as hitch pin, load, and disconnect status.Additional sensed parameters may include usage, wear, safety chainengagement, actuation is open or closed, proximity to cab/trailer andconnection or disconnection.

Coupler 110B: The coupler module 110B may communicate various dataparameters related to the function of a coupler and/or the conditionsunder which such operates. By way of a non-limiting example, the module110B may communicate data to identify connection status or the status ofa second lock or catch. Further, the module 110B may communicatediagnostic status such as load, and disconnect status. Additional sensedparameters may include usage, wear, proximity to cab/trailer, connectionor disconnection, and safety pin.

Sway controller 110C: The sway controller module 110C may communicatevarious data parameters related to the function of a sway controllerand/or the conditions under which such operates. By way of anon-limiting example, the module 110C may communicate data to identifyoutputs. Further, the module 110C may communicate diagnostic status suchas if and/or when a sway event is in progress or has occurred.Additional sensed parameters may include when and/or if a warning/safetysway condition exists and wheel speeds at the time of the condition.

Jack assemblies 110D: The jack assembly module 110D may communicatevarious data parameters related to the function of a jack assemblyand/or the conditions under which such operates. By way of anon-limiting example, the module 110D may communicate data to identifyposition, load, and effort. Further, the module 110D may communicatediagnostic status such as cycles. Additional sensed parameters mayinclude jail failure, wear/cycle, lubrication, electrical drive positionor level, warnings for load or overload conditions, assist in hookup,and proximity related to jack stow or work positions.

Brake controller 110E: The brake controller module 110E may communicatevarious data parameters related to the function of a brake controllerand/or the conditions under which such operates. By way of anon-limiting example, the module 110E may communicate data to identifyelectric over hydraulic dimming (EOH), configuration, outputs, boost,and gain. Further, the module 110E may communicate diagnostic statussuch as faults (e.g., open ground, short to ground, short to V_(bat),overload, etc.), and current voltages. Additional sensed parameters mayinclude warning or safety conditions such as power loss, connection ordisconnection, and default. Further communicated data may include sensorinputs for heat, wheel speed, and brake effort.

Pin Box 110F: The pin box module 110F may communicate various dataparameters related to the function of a pin box and/or the conditionsunder which such operates. By way of a non-limiting example, the module110F may communicate data to identify connection status, articulationproximity, and air ride. Further, the module 110F may communicatediagnostic status such as air bag failure, disconnection, load, highpin, and pressure. Additional sensed parameters may include autoinflate/deflate, load, tire pressure monitoring system (TPMS), andproximity.

Weight distribution 110G: The weight distribution module 110G maycommunicate various data parameters related to the function of a weightdistribution assembly and/or the conditions under which such operates.By way of a non-limiting example, the module 110G may communicate datato identify a load, and a level. Further, the module 110G maycommunicate diagnostic status such as load, conditions, bar disconnectstatus, and friction pad wear. Additional sensed parameters may includeusage, wear, load at head/base, level, proximity, missing clips, andspecial relationship to other assemblies such as motorized systemsincluding jack assemblies.

Provided is an exemplary the data collection and communication system ofthe present disclosure. The present disclosure, however, is not limitedto this example. The present teachings may include any combination ofeach of the components described above and below. For the sake ofbrevity not every combination is disclosed, but is contemplated by thepresent teachings. In this embodiment, a brake controller, such as onedisclosed by commonly owned U.S. Pat. No. 8,789,896 with is incorporatedby reference, has been configured to communicate and collect datarelated to its use and performance. The brake controller has beenconfigured to collect data and communicate data to a smartphone via awireless Bluetooth connection as illustrated by the various screenshotsof FIG. 8 and Attachment A. Attachment A accompanies this applicationand illustrates various data inputs that may be collected from the brakecontroller module 110E to a display 102 such as a smartphone or otherapplication on a mobile device. Notably, this disclosure contemplatesthat similar types of data may be collected by the various other modules110A, 110B, 110C, 110D, 110E, 110F, and 110G and communicated to asmartphone or other device through the network, via wired or wirelessconnections as described herein.

What has been described above includes examples of the presentspecification. It is, of course, not possible to describe everyconceivable combination of components or methodologies for purposes ofdescribing the present specification, but one of ordinary skill in theart may recognize that many further combinations and permutations of thepresent specification are possible. Each of the components describedabove may be combined or added together in any permutation to define thedata collection and communication system of the present disclosure.Accordingly, the present specification is intended to embrace all suchalterations, modifications and variations that fall within the spiritand scope of the appended claims. Furthermore, to the extent that theterm “includes” is used in either the detailed description or theclaims, such term is intended to be inclusive in a manner similar to theterm “comprising” as “comprising” is interpreted when employed as atransitional word in a claim.

Example 2

FIGS. 9 through 13D illustrate various embodiments of the invention. Inparticular, specific interactions between specific components are shownin flowchart format so as to highlight specific functions. It will beunderstood that these interactions and components may be incorporatedinto a system with additional components, all as disclosed above.

For example, FIG. 9 indicates the specific flow of actions between thetrailer brake controller and the jack. It may be possible to couplethese components—using these precise actions/functions—with otheraspects, such as a tire pressure monitoring system or a securing system.These additional components may add additional functionality but withoutaltering or diminishing the specific sequence illustrated in FIG. 9.

The specific embodiments contemplated by these examples are intended asnon-limiting. Also, conventional aspects of flowcharts will beappreciated by those of skill: as an example, diamond-shaped boxes inthe drawings represent decision points (or, in some cases, yes-nodeterminations made by data provided by the present system and/or thecomponents in question), while the arrows illustrate the progression ofevents. The Bluetooth symbol (

) generally indicates wireless communication between the components inall of the subgroupings of this Example 2, although this contextual useis not intended to limit the invention only to the use of Bluetoothprotocols.

Example 2A

FIG. 9 illustrates how the Trailer Brake Controller TBC leverages senseddata and inputs to exert control over the jack without the need forindependent user intervention. TBC receives input or sensed data,preferably in a wireless fashion, to continually verify coordinatedoperation of the system. Preliminary steps 900 are devoted todetermining whether the wheels of the vehicle are in motion, potentiallyby receiving the status of the ignition from the on board diagnostics orbased upon the observed wheel speed from any of the system components.The engagement status of the connection device (e.g., the kingpin of thefifth wheel hitch from a sensor located on that component) is alsoverified.

As noted in block 910, if the ignition is on and/or the speed is notequal to zero (either indicated forward motion or unintended backwardsrolling of the vehicle and/or trailer), a negative indication to thoseconditions reverts the system back to step 900 and continues in a loopto ensure real-time status and operation. If movement or ignition ispresent, kingpin engagement is also verified in step 910. If the kingpinis not engaged, actions 920 (both preferably wireless) are initiated tocreate an output to extend the jack and to warn driver via the brakecontroller unit display or interface (e.g., audible warning).Conversely, if the kingpin is engaged, a jack retraction output isgenerated in step 930 to continually confirm safe operation of theoverall system. Such automatic communication between devices is anexample of a “mesh network” in which the components may interactseamlessly, while providing status updates or other information to theuser.

Example 2B

FIG. 10 shows how operation of the trailer brake controller TBC may becoordinated with the trailer brake unit TB. In preliminary step 1000,stoplight or manual control is confirmed as active. If these items areinactive, the system will function on a continual loop until such actionis verified, resulting in a seamless, continuous approach to operation.

Step 1010 involves the calculation of a trailer brake control outputbased on sensed data (or inputs) indicative of deceleration, brakingeffort, gain, speed, boost, and/or a correction factor reflecting anynumber of variables that may be outside of the norm (e.g., in responseto weather conditions, trailer weight, level, etc.). This output iscommunicated as voltage V2 to the trailer brake unit, preferably via ahardwired connection to minimize any unintended failures and, moregenerally, to ensure the safest and most secure mode of operationbetween these critical units. Finally, this step also involves receiptof communication from the trailer brake unit.

Step 1030 verifies whether feedback was received from the brake unit viastep 1010. As with other aspects of the system, a negative responseinitiates periodic verification in of step 1030 to ensure continuous andseamless operation.

In the event feedback is detected in step 1030, step 1040 stores any newinformation, such as an updated correction factor (which addressesvoltage drop in the wires or connections caused by heavy current andwire resistance, as one example and is calculated, for example, by thetrailer brake controller based on V₁, V₂, and I₂) or other inputs fromthe trailer brakes. Step 1040 also returns operation back to step 1000to verify the appropriate correction factor (and/or other data received)is incorporated into future operation of the system.

As noted above trailer brakes TB receive voltage V2 from the trailerbrake controller. Step 1050 determines whether the voltage so receivedis stable by comparing it against voltage V_(th) for a fixed period oftime, such as 0.6 seconds (or any range from 0.1 to 1.0 seconds),Voltage V2 and current I2 are established and the brake unit TBcalculates the number of axles for braking in step 1060. Finally, theunit TB compares the calculated number of axles against a defaultsetting or input provided by another system component and sends awarning output to all components as appropriate to the circumstances. Ineither case, this final step 1070 produces an output, preferablycommunicated wirelessly, to reflect V2, I2, and the number of axles backto the brake controller TBC and, possibly, other system components,possibly relying on a mesh network.

Example 2C

FIG. 11 illustrates potential ways in which the communications deviceCOMM DEV of the system may be utilized, particularly with respect tosetting up the system (possibly including default settings for a varietyof components). Preliminary inputs are verified in step 1100, includingthe selection of the application and other user inputs. Informationabout the vehicle, the number of axles, the tongue weight of thetrailer, the overall trailer weight, and other pertinent information issolicited and entered through a corresponding number of different menusin step 1110. It will be understood that additional information can beinput in this manner.

Based at least in part upon the data entries from step 1110, thecommunications device COMM DEV generates appropriate outputs to thetrailer brake controller TBC and other system components, preferably viaa wireless connection, in step 1120. Also, this data may be output tothe memory inherent to any component(s) and/or information storagedevice associated with the system and/or internet or third party basedservice or server that is external to the system.

The storage device may compile data from several different trailers tocome up with statistical information. It can identify parameters out ofnormal values and send messages/warnings/cautions to the pertinenttowing systems and to the manufacturer. For example, if the gain is toolow for the weight of a trailer being towed by a relatively lightweightvehicle/truck, that may act as a warning to the driver about incorrectgain setting. While shown in this particular example, this approachapplies equally to all embodiments contemplated and described herein.

Example 2D

FIG. 12 illustrates how a variety of components may integrate in certainembodiments. Here, the interactions of trailer brake controller TBC,fifth wheel hitch 5^(th) Wheel, Communications Device, Storage Device,and Jack are shown. As noted above, wireless communication protocolswill simplify the installation and operation of these disparatecomponents.

As seen in step 1200, trailer brake controller TBC obtains the ignitionstatus, speed, and other information from the vehicle's on boarddiagnostics system II (OBDII). This information is then output to thecommunications device.

In parallel operation 1210 (i.e., the steps are independent of oneanother, although the information or subsequent operation of thecomponents may be iterative or interconnected), the fifth wheel hitchchecks for engagement status of its kingpin to its jaws. This senseddata is output to the communications device.

As indicated by parallel and/or responsive operation 1250, thecommunications device may, for all steps in this process, wirelesslytransmit event details, data, and/or operational logs to a storagedevice for immediate or future action, as well as to gather macro-scaledata to establish norms, warnings, caution signals, and/or statusreports for this single system or across a large number of independentsystems. In step 1220, the received inputs regarding vehicle movement(e.g., via ignition status and/or speed) and kingpin engagement mayresult in a display output 1230 indicating a warning as to the fifthwheel engagement status. Step 1230 creates appropriate outputs withrespect to extending or retracting the jack (thereby preventing thetowed product from being dropped into the vehicle). As such, FIG. 12further informs the processes contemplated by FIG. 9 above. As withother examples, FIG. 12 is a type of mesh network.

Particularly in FIG. 12 (but also as noted throughout this disclosure),the illustration of a fifth wheel hitch is exemplary. Other connectionsdevices, including but not limited to a gooseneck and the like, could besubstituted with minimal alterations to the overall process shownherein. These examples also illustrate how the data and status of thedifferent components of the distributed system (in towed and towingvehicles) can be communicated to each other to improve the safety andefficacy of each component and the overall system.

Example 2E

FIGS. 13A through 13C illustrate various inter-related actions of thetrailer brake controller TBC, the communications device, and the trailerbrakes. These figures further inform the discussion of FIG. 10 above andalso provide an example of a mesh network.

As seen in FIG. 13A, the trailer brake controller TBC determines whetherthe stoplight or manual control is active in step 1300. If these itemsare inactive, the system will function on a continual loop until suchaction is verified, resulting in a seamless, continuous approach tooperation. Step 1302 calculates a trailer brake controller output basedon a variety of factors, and this output may be transmitted directly tothe brakes, preferably via a hardwired connection.

Alternatively, in order to avoid potential voltage drop across the wire,the TBC may send the calculated PWM signal to the brake unit, which thengenerates the appropriate PWM braking signals. This requires the use oftrailer battery to power the brakes. Also in this step, wireless (orother) communication of the output may be sent to the communicationsdevice with corresponding inputs received from the communications deviceto further inform the calculations in this step. As such, step 1302 maybe iterative and continuously performed during operation of the trailerbrake controller.

FIG. 13B illustrates portions of the operation of the communicationsdevice. Step 1310 awaits inputs, preferably received wirelessly, fromother system components. Once received, step 1312 determines the originof the input, with particular distinctions made between trailer brakecontroller TBC and trailer braking unit TB (additional units could berecognized in this step, as acknowledged by the terminating lineextending from the right of these sequences). If the TBC is indicated asactive, step 1314 notes the TBC output voltage as V1 and further astatus to wait for input from the trailer brakes TB is indicated, withthe operation returning to step 1310 until that TB input is received.

If the input from step 1312 is associated with the trailer brakes TB,busy status is established in step 1316 (this status may be generatedand used at any step in this other operations disclosed herein whichcannot be interrupted). Also, the received voltage and current by thetrailer brakes are noted, respectively, as V2 and I2. Lastly, the statusof the communications device is set to wait for the TBC voltage to bereceived.

The voltages V1 and V2 are then checked for equivalence in step 1318 inorder to determine if the correction factor is appropriate. An updatedcorrection factor may be calculated, if needed, based on V1, V2, and I2.Finally, in step 1319, the number of axles is verified and wirelesscommunications, via Bluetooth and/or traditional Wi-Fi signals, informthe trailer brake controller TBC and provide representative data (e.g.,event information, data, etc.) to the memory or information storagedevice in order to allow for immediate or future actions, as well as togather macro-scale data to establish norms, warnings, caution signals,and/or status reports for this single system or across a large number ofindependent systems. This macro-scale data and system actions can alsorelate to preventive maintenance, software status, and other similarfunctions.

Finally, with reference to FIG. 13C, trailer brakes TB establish thenature of voltage in step 1320, with return loops to see if voltage isreceived and, if so, if that voltage has yet stabilized (i.e., V2>thanV_(th)). In this context, V_(th) is a threshold voltage when the voltageat the brakes is stable. Typically, V_(th) should be greater than thefirst three measurements, with ˜0.7 seconds of delay providing enoughtime for stabilizations (although any type of delay may be utilized,those disclosed here are merely exemplary). Alternatively, these threemeasurements could be used as V_(th). This looped approach effectivelyestablishes a feedback loop to make sure that the voltage reading usedis not taken at a point when the voltage is still rising. Once thevoltage is received and stable, settings for voltage V2 and current I2are established and the number of axles is calculated in step 1322. Step1324 compares the calculated number of axles against a default input andan appropriate warning output may be produced. In either instance, V2,I2, and the number of calculated axles are output, preferablywirelessly, to the communication device in step 1326.

Example 3

FIG. 14 provides a generic schematic indicating the relationship of acomponent 1400 within the system. Component 1400 may be anyone of thecomponents identified above, including those associated with theelectronics, connection, accessories, and/or the master controller.Power is received by component 1400 from a power supply 1410, such as abattery or other power supply as noted herein.

Sensors/inputs 1420 and 1422 may originate from sensors and/or userinterfaces. These inputs are received by the component 1400 for furtheruse by the system. While only two are illustrated, any number of inputscould be generated by any number of sensors or interfaces. The sensorsmay be selected from those identified herein, with particular attentiongiven to the desired functionality of component 1400.

Component 1400 generates outputs 1430, 1432 that may be transmitted toany combination of other components (not shown) within the system. Whileonly two are illustrated, any number of outputs could be generated byany number of sensors or interfaces. These outputs may simply passthrough the data received as sensors/inputs 1420, 1422. In thealternative, component 1400 may include logic manipulation of the dataprior to generating outputs 1430, 1432. Also, the outputs may beprovided as wired or wireless signals. In the event the latter areproduce, such signals would not necessarily be connected or directed atany single component or direction, whereas wired connections mustnecessarily lead to another component (not shown). Separately, component1400 is configured to provide data to one or more communications devices1440, 1442. As with outputs 1430, 1432, these data signals may betransmitted to the communications devices 1440, 1442 via wired orwireless connections. Also, any numbers of communications devices arecontemplated even though two are shown. Communications devices 1440,1442 represent devices that are external to the system, such as internetor third-party based servers and services.

The system and components described above allows a plurality of towingaccessory devices to work in concert with our without humanintervention. Moreover, the system allows the gathering of informationregarding the operation of such towing accessory devices. The system maynot provide a master slave type of control. Instead, it is a dynamicsystem that takes information from the various towing accessory devicesas well as other sources (available information, user information or acombination of such) to generate actions by the various towing accessorydevices. The plurality of towing accessory devices may communicatedirectly with one another (such as in a mesh network), through acommunication device and/or through an electronic storage device. Thesystem provides this communication to cause the towing accessory devicesto act, not just as a warning system or status indicator. While thosemay occur, the action generated is part of the system. The components ofthe system may include at least one or a plurality of towing accessorydevices, a master controller, communication device, user interface andan electronic storage device. However, some of these components may becombined in a single device or split among multiple devices. The systemis expandable—different towing accessory devices may be added or towingaccessory devices may be replaced with the system. The new towingaccessory devices may be easily integrated into the system. The systemalso allows software, system settings or other information to be updatedsuch as through the electronic storage device, master controller,communication device, or a combination of such devices.

Further, the master controller or controller could be a more powerfuldevice, e.g., a trailer brake controller. However, it is not limited tosuch.

Further still, the electronic storage device may take collectiveinformation and send directions to select towing accessory devices toact on it. The electronic storage device may create profile data andhelp with optimization of designs of the towing accessory devices. Thisuser profile information may provide information to the user and to themanufacturer of the system and/or the towing accessory devices. Thesystem may also act as a theft deterrent device. The system may preventall actions on the towing accessory devices if a biometric sensor on thesystem does not identify a predetermined user, such as by way of anon-limiting example, through a retinal detector and/or finger printdetector.

The date obtained from the system may permit the manufacturer to be morein touch with the end user. It may allow the manufacturer to provideusers with recommendations as to the settings of the various towingaccessory devices or uses of the towing accessory devices.

As used herein, the terms “component,” “module,” “system,” “interface,”“platform,” “service,” “framework,” “connector,” “controller,” or thelike are generally intended to refer to a computer-related entity. Suchterms may refer to at least one of hardware, software, or software inexecution. For example, a component may include a computer-processrunning on a processor, a processor, a device, a process, a computerthread, or the likes. In another aspect, such terms may include both anapplication running on a processor and a processor. Moreover, such termsmay be localized to one computer and/or may be distributed acrossmultiple computers.

While methods may be shown and described as a series of blocks, it isnoted that associated methods or processes are not limited by the orderof the blocks. It is further noted that some blocks and correspondingactions may occur in different orders or concurrently with other blocks.Moreover, different blocks or actions may be utilized to implement themethods described hereinafter. Various actions may be completed by oneor more of users, mechanical machines, automated assembly machines(e.g., including one or more processors or computing devices), or thelike.

What is claimed is:
 1. A control system for active control of externalvehicle components, the control system comprising: a trailer brakecontroller; a tire pressure monitoring system operatively coupled withthe trailer brake controller; and a controller in operativecommunication with at least one of the tire pressure monitoring systemand the trailer brake controller to receive data with respect to thetire pressure monitoring system and wherein the controller processes thedata and sends a direction to act to the trailer brake controller. 2.The control system of claim 1, wherein the controller is integrated intothe trailer brake controller.
 3. The control system of claim 1 furthercomprising a user interface operatively coupled with the trailer brakecontroller.
 4. The control system of claim 3, wherein a status of thetire pressure monitoring system is displayed on the user interface. 5.The control system of claim 1, further comprising a user interface,wherein the user interface comprises at least one of the following: asmartphone, tablet, computer, and user interface of a trailer brakecontroller.
 6. The control system of claim 1, wherein the controller isin operative communication with both the tire pressure monitoring systemand the trailer brake controller and the operative communication iswireless.
 7. The control system of claim 1, wherein the controllerreceives information wirelessly from at least one of an internet-baseddata server and a private party data server.
 8. The control system ofclaim 7, wherein the information received by the controller relates toenvironmental conditions.
 9. The control system of claim 1, wherein thecontroller sends information wirelessly to at least one of aninternet-based data server and a private party data server.
 10. Thecontrol system of claim 9, wherein the information sent by thecontroller relates to diagnostic information of the tire pressuremonitoring system.
 11. The control system of claim 10, wherein the atleast one of the internet-based data server and the private party dataserver modifies an operating condition of the trailer brake controller.12. A control system for active control of external vehicle components,the control system comprising: a trailer brake controller; a tirepressure monitoring system operatively coupled with the trailer brakecontroller; and a controller in operative communication with at leastone of the tire pressure monitoring system and the trailer brakecontroller receives data regarding the tire pressure monitoring systemand wherein the controller processes the data and sends a direction tothe trailer brake controller.
 13. The control system of claim 12,wherein the tire pressure monitoring system provides an output to thecontroller indicating rotation of a wheel.
 14. The control system ofclaim 12, wherein the tire pressure monitoring system provides an outputto the controller indicating current voltage of a vehicle battery. 15.The control system of claim 12, wherein the tire pressure monitoringsystem provides an output to the controller indicating a recommendedpressure of a tire of a trailer.
 16. The control system of claim 12,wherein the tire pressure monitoring system provides an output to thecontroller indicating pressure of a tire of a trailer via a pressuretransducer.
 17. The control system of claim 12, wherein the tirepressure monitoring system provides an output to the controllerindicating a weight of a trailer exceeding a predetermined amount.
 18. Asystem comprising: a trailer brake controller comprising a tire pressuremonitoring system operatively and wirelessly coupled with the trailerbrake controller; a second towing accessory device comprising a secondsensor, the trailer brake controller and second towing accessory devicesin operative communication; and a communication device in operativecommunication with the tire pressure monitoring system, wherein datafrom the tire pressure monitoring system is communicated to thecommunication device and the communication device sends instructions tothe second towing accessory to generate an action for the second towingaccessory device.